Abstract: A system and method of providing resource management in association with extensible Java Server Pages are provided. The system and method provide an interface for defining alternative input source, resource path and compilers for generating JSP servlets for processing JSP requests. A JSP provider may define an extensible translation context that identifies whether default translation operations or extensible translation operations are to be performed. With regard to extensible translation operations, the provider may establish one or more of an extensible input source factory, an extensible resource factory and an extensible compiler factory. These factories provide a mechanism through which input source objects, resource objects, and compiler objects for alternative translation and compilation of the JSP servlet.

Abstract: Extensible URI-pattern-based servlet request processing frameworks process and respond to requests for resources sent over a network by client programs to application programs in multi-tiered data processing systems. An extension processor component, an improved web container; and an improved web application architecture form the framework. The extension processor component includes one or more extension processor factories, each of which generates a single type of extension processor to handle specific application components. Each extension processor is adapted to respond to a request having a declared pattern. The extension processor factory resides within the web container and provides a list of patterns for which it is responsible. The extension factory also instantiates an extension processor to respond to a request having a pattern that matches that extension processor's declared pattern.

Abstract: A system and method of providing resource management in association with extensible Java Server Pages are provided. The system and method provide an interface for defining alternative input source, resource path and compilers for generating JSP servlets for processing JSP requests. A JSP provider may define an extensible translation context that identifies whether default translation operations or extensible translation operations are to be performed. With regard to extensible translation operations, the provider may establish one or more of an extensible input source factory, an extensible resource factory and an extensible compiler factory. These factories provide a mechanism through which input source objects, resource objects, and compiler objects for alternative translation and compilation of the JSP servlet.

Abstract: A method and apparatus for providing a pluggable and extendable J2EE architecture are provided. The method and apparatus provide mechanisms for defining extension points within modules of the J2EE application and mechanisms for defining plug-in or extension modules that may be integrated into the J2EE application via these extension points. In addition, a mechanism for merging the plug-in or extension modules into the J2EE application at deployment is provided such that all of the information necessary for generating instantiations of the plug-in or extension modules is integrated into the J2EE application configuration files. As a result, an integrated J2EE application is made possible from a modularized and extendable development of the J2EE application.

Abstract: Method, system and computer program product are provided to increase the efficiency of the development of Java Enterprise Edition (J2EE) applications. A project may be divided into modules which may be developed by independent teams. The files within each module are classified as independent of resources in other modules or dependent. Independent files may be packaged into a single, integrated web application archive (WAR) file without further processing. Corresponding dependent files are compared and any conflicts are resolved. The resulting files may then be packaged into the WAR file.

Abstract: A method, apparatus, and computer instructions for a configurable JavaServer pages processing framework to process JavaServer pages (JSP). A JSP document or page is translated into a document object model (DOM) object that encapsulates elements of the JSP. The syntax of the JSP is validated by a JSP translator with built-in classes and errors are returned if necessary. A JSP visitor configuration file, which defines user configured classes and sequence of execution, is used by the JSP translator to invoke methods of user-defined classes in the order specified by the user to process or visit elements of the DOM object. Result of user-defined class processing may be passed from one class to another within the set.