Home >> All >> org >> apache >> jasper >> [ compiler Javadoc ]

•	org.apache.jasper.compiler.tagplugin.* (2)

• org.apache.jasper.compiler: Javadoc index of package org.apache.jasper.compiler.


Package Samples:

• org.apache.jasper.compiler.tagplugin

Classes:

• TldLocationsCache: A container for all tag libraries that are defined "globally" for the web application. Tag Libraries can be defined globally in one of two ways: 1. Via elements in web.xml: the uri and location of the tag-library are specified in the element. 2. Via packaged jar files that contain .tld files within the META-INF directory, or some subdirectory of it. The taglib is 'global' if it has the element defined. A mapping between the taglib URI and its associated TaglibraryInfoImpl is maintained in this container. Actually, that's what we'd like to do. However, because of the way the classes TagLibraryInfo ...
• PageDataImpl: An implementation of javax.servlet.jsp.tagext.PageData which builds the XML view of a given page. The XML view is built in two passes: During the first pass, the FirstPassVisitor collects the attributes of the top-level jsp:root and those of the jsp:root elements of any included pages, and adds them to the jsp:root element of the XML view. In addition, any taglib directives are converted into xmlns: attributes and added to the jsp:root element of the XML view. This pass ignores any nodes other than JspRoot and TaglibDirective. During the second pass, the SecondPassVisitor produces the XML view, ...
• ErrorDispatcher: Class responsible for dispatching JSP parse and javac compilation errors to the configured error handler. This class is also responsible for localizing any error codes before they are passed on to the configured error handler. In the case of a Java compilation error, the compiler error message is parsed into an array of JavacErrorDetail instances, which is passed on to the configured error handler.
• ParserController: Controller for the parsing of a JSP page. The same ParserController instance is used for a JSP page and any JSP segments included by it (via an include directive), where each segment may be provided in standard or XML syntax. This class selects and invokes the appropriate parser for the JSP page and its included segments.
• JspRuntimeContext: Class for tracking JSP compile time file dependencies when the &060;%@include file="..."%&062; directive is used. A background thread periodically checks the files a JSP page is dependent upon. If a dpendent file changes the JSP page which included it is recompiled. Only used if a web application context is a directory.
• ErrorHandler: Interface for handling JSP parse and javac compilation errors. An implementation of this interface may be registered with the ErrorDispatcher by setting the XXX initialization parameter in the JSP page compiler and execution servlet in Catalina's web.xml file to the implementation's fully qualified class name.
• TagPlugin: This interface is to be implemented by the plugin author, to supply an alternate implementation of the tag handlers. It can be used to specify the Java codes to be generated when a tag is invoked. An implementation of this interface must be registered in a file named "tagPlugins.xml" under WEB-INF.
• JasperTagInfo: TagInfo extension used by tag handlers that are implemented via tag files. This class provides access to the name of the Map used to store the dynamic attribute names and values passed to the custom action invocation. This information is used by the code generator.
• Validator: Performs validation on the page elements. Attributes are checked for mandatory presence, entry value validity, and consistency. As a side effect, some page global value (such as those from page direcitves) are stored, for later use.
• FileDeclarationPhase: If a generator wants to output stuff at "file scope" in the generated servlet class, it should implement this interface. The code would go outside the class body. (For example non-public support classes can be generated this way)
• Parser: This class implements a parser for a JSP page (non-xml view). JSP page grammar is included here for reference. The token '#' that appears in the production indicates the current input token location in the production.
• ELFunctionMapper: This class generates functions mappers for the EL expressions in the page. Instead of a global mapper, a mapper is used for ecah call to EL evaluator, thus avoiding the prefix overlapping and redefinition issues.
• ELParser: This class implements a parser for EL expressions. It takes strings of the form xxx${..}yyy${..}zzz etc, and turn it into a ELNode.Nodes. Currently, it only handles text outside ${..} and functions in ${ ..}.
• SunJavaCompiler: The default compiler. This is the javac present in JDK 1.1.x and JDK 1.2. At some point we need to make sure there is a class like this for JDK 1.3, and other javac-like animals that people want to use.
• TagPluginContext: This interface allows the plugin author to make inqueries about the properties of the current tag, and to use Jasper resources to generate direct Java codes in place of tag handler invocations.
• JspReader: JspReader is an input buffer for the JSP parser. It should allow unlimited lookahead and pushback. It also has a bunch of parsing utility methods for understanding htmlesque thingies.
• ELNode: This class defines internal representation for an EL Expression It currently only defines functions. It can be expanded to define all the components of an EL expression, if need to.
• SmapGenerator: Represents a source map (SMAP), which serves to associate lines of the input JSP file(s) to lines in the generated servlet in the final .class file, according to the JSR-045 spec.
• ClassDeclarationPhase: When a generator implements ClassDeclarationPhase, its generate method will only be invoked while generating the servlet's class body and not during the service method phase.
• JDTCompiler: JDT class compiler. This compiler will load source dependencies from the context classloader, reducing dramatically disk access during the compilation process.
• ImplicitTagLibraryInfo: Class responsible for generating an implicit tag library containing tag handlers corresponding to the tag files in "/WEB-INF/tags/" or a subdirectory of it.
• CharDataGenerator: CharDataGenerator generates the character data present in the JSP file. Typically this is HTML which lands up as strings in out.println(...).
• Node: An internal data representation of a JSP page or a JSP docuement (XML). Also included here is a visitor class for tranversing nodes.

Home | Contact Us | Privacy Policy | Terms of Service