Home >> All >> org >> apache >> bsf >> [ util Javadoc ]

•	org.apache.bsf.util.cf.* (2)	•	org.apache.bsf.util.event.* (21)
•	org.apache.bsf.util.event.adapters.* (13)	•	org.apache.bsf.util.event.generator.* (4)
•	org.apache.bsf.util.type.* (2)

• org.apache.bsf.util: Javadoc index of package org.apache.bsf.util.


Package Samples:

• org.apache.bsf.util.event.adapters
• org.apache.bsf.util.event.generator
• org.apache.bsf.util.event
• org.apache.bsf.util.cf
• org.apache.bsf.util.type

Classes:

• BreakPoint: This is a class for the debug manager to remember a breakpoint. Breakpoints are set globally to a JVM, that is, globally to all BSFManager/BSFEngine created in the JVM. A breakpoint is either at a line (defined by '\n') or an (char) offset in a document. NOTE: There is no correspondance so far... so for instance, if a breakpoint is defined at an offset, it cannot be manipulated later as defined with a line, although conceptually there is an equivalence between lines and offsets. A document is for instance a JSP in Tomcat/Jasper framework. Its name is given when evaluating/executing a function or ...
• EventAdapterRegistry: The EventAdapterRegistry is the registry of event adapters. If a desired adapter is not found, the adapter will be dynamically generated when lookup is attempted. Set the dynamic property to false to disable this feature. This implementation first looks for an adapter in its lookup table and if it doesn't find one looks for a standard implementation of that adapter in the org.apache.bsf.util.event.adapters package with a standard naming convention. The naming convention it assumes is the following: for event listener type a.b.c.FooListener , it loads an adapter of type org.apache.bsf.util.event.adapters.a_b_c_FooAdapter ...
• EventAdapter: EventAdapter is the interface that all event adapters must implement in order to work with the automatic event adapter generation model. This interface requires that the adapter implement a method that allows setting the event processor delegated to process the event after the adapter has received the event from the event source. The task of any event adapter is to receive the event and then delegate it to the event processor assigned to it, using either eventProcessor.processEvent or eventProcessor.processExceptionableEvent.
• CFDriver: This is an example of how a CodeFormatter bean can be used. The CFDriver is a stand-alone tool that will instantiate a CodeFormatter bean, configure it according to your command-line arguments, and invoke the formatting. Since the default source of input is stdin , and the default target for output is stdout , a CFDriver can also be used as a filter.
• CodeFormatter: A CodeFormatter bean is used to format raw Java code. It indents, word-wraps, and replaces tab characters with an amount of space characters equal to the size of the indentationStep property. To create and use a CodeFormatter , you simply instantiate a new CodeFormatter bean, and invoke formatCode(Reader source, Writer target) with appropriate arguments.
• DocumentCell: A DocumentCell allows the debug manager to keep track of known documents for which it has breakpoints. When a debugger sets a breakpoint, it specifies a document. This is when a DocumentCell is created for that document (identified through its URI). The debug manager will keep the document cells at least as long as there is breakpoints known and as long as there are engines known to currently execute the document.
• ObjectRegistry: The ObjectRegistry is used to do name-to-object reference lookups. If an ObjectRegistry is passed as a constructor argument, then this ObjectRegistry will be a cascading registry: when a lookup is invoked, it will first look in its own table for a name, and if it's not there, it will cascade to the parent ObjectRegistry . All registration is always local. [??]
• EventProcessor: EventProcessor is the interface that event adapters use to delegate events they received to be delivered to the appropriate target. They can simply deliver the event using processEvent or, if the event can be excepted to, via processExceptionableEvent (in which case the adapter is expected to forward on an exception to the source bean).
• TypeConvertor: A TypeConvertor is used to convert an object of one type to one of another type. The convertor is invoked with the class of the from object, the desired class, and the from object itself. The convertor must return a new object of the desired class.
• BSFFunctions: This is a utility that engine implementors may use as the Java object they expose in the scripting language as "bsf". This has essentially a subset of the methods in BSFManager plus some stuff from the utils. Currently used by Javascript (Rhino) & BML.
• Bean: A Bean is the class used to represent a bean: it holds a type and a value. This is needed because otherwise we can't represent the types of null-valued beans (or primitives) correctly. This was originally in the BML player.
• EventAdapterImpl: EventAdapterImpl is a default implementation of the EventAdapter interface that specific event adapters may choose to subclass from instead of implementing the interface themselves. Saves 5 lines of code mebbe.
• IndentWriter: An IndentWriter object behaves the same as a PrintWriter object, with the additional capability of being able to print strings that are prepended with a specified amount of spaces.
• Bytecode: Bytecode handling utilities Handle standard byte arrays as defined in Java VM and Class File 5 April 1999 - functions to append Class File byte subarrays into a Class File byte array
• TypeConvertorRegistry: The TypeConvertorRegistry is the registry of type convertors. It has lookup and register capabilities based on the types to be converted as well as by some object key.
• BSFEngineImpl: This is a base implementation of the BSFEngine interface which engine implementations may choose to extend to get the basic methods of the interface implemented.
• CodeBuffer: A CodeBuffer object is used as a code repository for generated Java code. It provides buffers which correspond to the various sections of a Java class.
• ReflectionUtils: This file is a collection of reflection utilities. There are utilities for creating beans, getting bean infos, setting/getting properties, and binding events.
• ByteUtility: Byte handling utilities 5 April 1999 - functions to append standard types to byte arrays functions to produce standard types from byte arrays
• ScriptSymbolTable: An ScriptSymbolTable object is used by a CodeBuffer object to implement nested scopes.
• EngineUtils: This class contains utilities that language integrators can use when implementing the BSFEngine interface.
• BSFClassLoader: This class loader knows to load a class from the tempDir dir of the environment of the given manager.
• MethodUtils: This file is a collection of reflection utilities for dealing with methods and constructors.
• ObjInfo: An ObjInfo object is used by a compiler to track the name and type of a bean.

Home | Contact Us | Privacy Policy | Terms of Service