| Home >> All >> org >> apache >> bsf >> [ dbline Javadoc ] |
org.apache.bsf.dbline: Javadoc index of package org.apache.bsf.dbline.
Package Samples:
org.apache.bsf.dbline
Classes:
Buffer: A buffer represents a document such as a JSP. Note that lines start at zero, so the first line has a line number of zero. A document is described by its URI as known in the servlet engine. The URI includes the Web application prefix. For instance: /examples/jsp/cal/cal1.jsp with /examples being the application prefix. Note: the name is the shortname, that is, the last name of the URI. This allows easy manipulation from the command line in the debugger.
BreakPoint: This class instances represent breakpoints as known by the client debugger. This is fairly straightforward code. Note the simple but efficient allocation scheme for breakpoint identifiers. Whatever scheme is used, these identifiers should remain unique throughout an entire debug session. Note also that these breakpoins are only supporting a definition based on line numbers, char offsets are not supported.
Context: Context objects represent remote JsContext in the JavaScript engine. JsContext are the JavaScript ECMA 1.3 contexts, forming the execution stack of the engine. Typically, the debugger will create a stack of Context objects mapping to the JavaScript context in the engine.
Callbacks: This object is the remote object that will be passed to the remote debug manager as both the BSFDebugger and the JavaScript-specific callback object. Note: there is no obligation that both be implemented by the same object.
JsObjectProxy: This is a proxy for remote objects in the JavaScript engine. Each proxy is given a unique identifier which allows an easy manipulation from the command line debugger.
FnOrScript: Insert the type's description here. Creation date: (9/4/2001 1:14:44 PM)
JsDb
| Home | Contact Us | Privacy Policy | Terms of Service |