| Home >> All >> org >> apache >> bsf >> engines |
Package Samples:
• org.apache.bsf.engines.activescript
• org.apache.bsf.engines.jacl
• org.apache.bsf.engines.javascript
• org.apache.bsf.engines.xslt
• org.apache.bsf.engines.jpython
• org.apache.bsf.engines.netrexx
• org.apache.bsf.engines.jython
• org.apache.bsf.engines.javaclass
• org.apache.bsf.engines.java
Classes:
• JavaEngine: This is the interface to Java from the Bean Scripting Framework. The Java code must be written script-style -- that is, just the body of the function, without class or method headers or footers. The JavaEngine will generate those via a "boilerplate" wrapper: import java.lang.*; import java.util.*; public class $$CLASSNAME$$ { static public Object BSFJavaEngineEntry(org.apache.bsf.BSFManager bsf) { // Your code will be placed here } } $$CLASSNAME$$ will be replaced by a generated classname of the form BSFJava*, and the bsf parameter can be used to retrieve application objects registered with the ...
• NetRexxEngine: This is the interface to NetRexx from the Bean Scripting Framework. The NetRexx code must be written script-style, without a "class" or "properties" section preceeding the executable code. The NetRexxEngine will generate a prefix for this code: class $$CLASSNAME$$; method BSFNetRexxEngineEntry(bsf=org.apache.bsf.BSFManager) public static; $$CLASSNAME$$ will be replaced by a generated classname of the form BSFNetRexx*, and the bsf parameter can be used to retrieve application objects registered with the Bean Scripting Framework. If you use the placeholder string $$CLASSNAME$$ elsewhere in your script ...
• BreakPoint: Materializes a breakpoint. A breakpoint can be defined at a line number or an offset character in its document. For JavaScript, we only support lineno for the underlying Rhino engine does support only the line numbers. Note: this is unfortunate for this prevents setting a breakpoint on different statements on the same line... A breakpoint is remembered at either the document level (DocumentCell) or the function/script level (FnOrScript). It is remembered at the document level when a FnOrScript is not yet known for the breakpoint line number. When a matching FnOrScrip will become known (compiled ...
• DocumentCell: A document cell materializes a known document. A document is a container for scripts or functions in JavaScript. The document is known as soon as a function or script is compiled in the engine. Compilation occurs as a side-effect of evaluating or executing a function or a script. Upon the first loading of a function or script of a document, the document becomes known and the debug manager is notified of the load. The debug manager will in turn notify the engine of all the known breakpoints for that document. When a breakpoint is propagated from the debug manager to an engine, the document will ...
• FnOrScript: This class represents a function or script, that is, a piece of a document that is provided to the JavaScript engine for evaluation, execution, or simply compilation. A FnOrScript represents a range of lines or characters in its document. For now, Rhino only supports ranges of lines, really, but the code for offsets is there anyway. Warning: Offsets have never been quite tested yet... A FnOrScript has compilation units. When Rhino compiles a function or a script, even in interpreted mode where the compilation is done to JavaScript bytecode, it calls back its debugger with different compilation ...
• CompilationUnit: A compilation unit is a Rhino concept. When a piece of script is provided for eval or execute to a Rhino engine, it is compiled down to either JavaScript or Java bytecode. In debug mode, only the compilation down to JavaScript bytecode is supported. During the compilation process, the original piece of script is sliced into compilation units. For instance, the script text may contain a function declaration and an expression to eval. The compilation will result in two compilation units: the function and the expression. Each compilation unit will correspond to a range of the lines of the original ...
• ActiveScriptEngine: This is the interface to active scripting engines from the Bean Scripting Framework. This code uses John Ponzo's IBM Active Scripting Toolkit to tie in active scripting engines to BSF. This class implements Runnable to create a thread. This thread is to exclusively access the scripting engine. All methods from this class to the engines is proxied over to the engine thread for execution. Why? Because, MS engines are implemented to only be accessed from ONE thread.
• JavaScriptEngine: This is the interface to Netscape's Rhino (JavaScript) from the Bean Scripting Framework. The original version of this code was first written by Adam Peller for use in LotusXSL. Sanjiva took his code and adapted it for BSF.
• XSLTEngine: Xerces XSLT interface to BSF. Requires Xalan and Xerces from Apache. This integration uses the BSF registry to pass in any src document and stylesheet base URI that the user may wish to set.
• vbEmpty: This class is only used as an ojbect to be returned to scripting engine the VB_EMPTY variant which is not necessarly threated the same as null.
• JythonEngine: This is the interface to Jython (http://www.jython.org/) from BSF. It's derived from the JPython 1.x engine
• JavaClassEngine: This is the interface to scripts consisting of Java objects from the Bean Scripting Framework.
• JaclEngine: This is the interface to Scriptics's Jacl (Tcl) from the Bean Scripting Framework.
• JsContextStub: Insert the type's description here. Creation date: (8/23/2001 4:16:50 PM)
• JsObjectStub: Insert the type's description here. Creation date: (8/24/2001 9:54:48 AM)
• JsEngineStub: Insert the type's description here. Creation date: (9/6/2001 1:21:46 PM)
• JPythonEngine: This is the interface to JPython (http://www.jpython.org/) from BSF.
• JavaOLEENUMVAR
• JavaBean
• COMIDispatchBean
• JavaBeanAddEventListener
• BSFCommand
• RhinoContextProxy
| Home | Contact Us | Privacy Policy | Terms of Service |