Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

javax.ide.extension.spi.* (19)

javax.ide.extension: Javadoc index of package javax.ide.extension.


Package Samples:

javax.ide.extension.spi: The ide package is where all JSR 198 packages are rooted.  

Classes:

I18NCharVisitor: An element visitor that processes xml elements of type i18n_char. If the element has an rskey attribute and an ancestor extension element defined a bundle using the rsbundle attribute, this implementation will use ResourceBundle.getBundle() to load a string resource from the bundle class. If no rskey attribute is present, the text of the element will be used instead. In either case, characterValue( ElementContext, char ) 55 is called with the first non-whitespace character of the resulting string. An error is logged if the rskey attribute is present on the element but no rsbundle was defined in ...
Stack: Convenient implementation of a Last In First Out (LIFO) stack. This implementation differs from the one in java.util.Stack in two ways. First, like most of the collection APIs, it is unsynchronized for better performance when synchronization is not required. If a synchronized stack is required, you can use the Collections.synchronizedCollection() 55 method to retrieve a synchronized instance. Second, it does not expose its internal implementation via its superclass. Extending AbstractCollection instead of Vector allows objects of this class to be used interchangably with other collection framework ...
I18NStringVisitor: An element visitor that processes xml elements of type i18n_string. If the element has an rskey attribute and an ancestor extension element defined a bundle using the rsbundle attribute, this implementation will use ResourceBundle.getBundle() to load a string resource from the bundle class. If no rskey attribute is present, the text of the element will be used instead. In either case, string( ElementContext, String ) 55 is called with the resulting string. An error is logged if the rskey attribute is present on the element but no rsbundle was defined in an ancestor extension element.
TypeInfo: Record of information identifying an object type. The information used to initialize this class comes from an extension manifest. The information kept in this class includes the object type identifier and the object javax.ide.util.MetaClass . Object type identifiers are unique labels given to objects declared in an extension manifest. By convention these labels are dash or dot separated strings. Sample identifiers can be found in the javax.ide.IDEConstants class.
ExtensionSource: Represents an extension source. An extension source is typically a JAR file in an IDE specific location for extension jar files. However, an ExtensionSource could potentially be some other abstract representation of an extension. One example would be an as-yet unbundled extension manifest launched from the extension development runtime of an IDE. A default implementation of this interface is provided in JARExtensionSource.
MetaClassVisitor: An abstract implementation of a visitor for manifest elements which represent meta classes. Subclasses provide an implementation of the metaClass( ElementContext, MetaClass ) 55 to process the meta class created for the visited xml element.
BooleanVisitor: Visitor for handling elements of type xs:boolean. Subclasses provide an implementation of booleanValue( ElementContext, boolean ) 55 , which is called when a boolean value is retrieved for the element.
DefaultExtension: This class maintains general information about an extension. Information gathered from the extension manifest is stored in this class. Such information include the extension's id, owner, version information, etc.. IDE providers can use this class to to record the extension information section of the extension manifest.
DefaultHookVisitorFactory: The default implementation of the visitor factory for hooks. This implementation returns the default implementations of all standard hooks defined by the JSR-198 spec and provides a registerHookVisitor() method used by the hook-handler-hook to register custom hooks declared in the manifest.
ElementVisitor: ElementVisitor is responsible for visiting elements in an XML file processed by an XML parser used by a JSR-198 compatible IDE. Implementations of this class usually provide an implementation for the start() and end() methods.
ExtensionHook: An extension hook is responsible for processing information from the extension manifest for a particular feature and making this information available to the service responsible for managing the functionality provided by the hook.
ListenerInfo: Records information defining the listener class to be instantiated when an event on the target object occurs. The information used to initialize this class comes from an extension manifest editor-hook section.
ElementContext: ElementContext provides information about the current element being visited and provides utilities for processing child elements, reporting logging messages and storing information for use by other visitors.
Feature: Feature information gathered from processing the feature-hook section of the extension manifest. The information recorder here describes the functionality an extension provides in a user visible way.
FeatureRegistry: The feature registry provides access to information about extensions which are declared as features in their extension manifest. It is only intended to be used by integrators writing IDE support for JSR198.
Extension: Information gathered from the Extension Deployment Descriptor is stored by implementations of this interface. Such information include the extension's id, owner, version information, etc.
HookHandlerHook: The hook-handler-hook implementation. This implementation takes a DefaultHookVisitorFactory in its constructor and registers handlers for custom hooks through this factory.
BaseExtensionVisitor: A base class for ExtensionVisitor which processes the attributes of the extension tag. This is also used by a minimal processor in DependencyTree.
DefaultElementContext: A default XML context implementation. This provides access to methods that change the context and should only be used by ExtensibleSAXHandler.
DependencyTree: DependencyTree is responsible for determining dependencies between extensions and providing a load order that satisfies those dependencies.
ElementName: Represents a qualified element name in XML. A qualified element name consists of a namespace URI (which may be null) and a local name.
JARExtensionSource: A default implementation of ExtensionSource which loads an extension manifest from the META-INF/extension.xml entry of a JAR file.
ElementVisitorFactory: The element visitor factory is used to create or retrieve visitors for specific xml elements while traversing xml.
DynamicHook: An implementation of ExtensionHook that automatically populates model objects using reflection.

Home | Contact Us | Privacy Policy | Terms of Service