Abstract: A computerized method and a system for direct deploy of static content. Static content is received at a deployment framework of an application server. The content is forwarded to a content deployment extension (CDE) for implementing the deployment of the content on the applications server. The application server operates in online mode during the deployment. The CDE selects an appropriate content handler to handle the deployment of the content. The content is deployed by the content handler on the application server in online mode. The CDE receive a feedback from the deployment of the static content.

Abstract: A system and method for integrating a diverse set of web/remote user interface technologies into one runtime architecture using a Web container extension is described. This integration simplifies execution, cross-usage, and technology integration between different user interface technologies and other application server offerings.

Abstract: A system and method for integrating a diverse set of web/remote user interface technologies into one runtime architecture using a Web container extension is described. This integration simplifies execution, cross-usage, and technology integration between different user interface technologies and other application server offerings.

Abstract: A method and system to provide easy access to factories in a naming service. The system receives an indication that a factory is needed by a client. A plurality of resolvers are checked in turn to find the factory indicated. If a resolver that can provide the factory is found, the factory is returned to the client. In one embodiment, resolvers register with a resolver manager that performs the checking in response to a naming operation. Because the resolver manager can access all registered resolvers, access to the factories is independent of a class path of the user.

Abstract: A computerized method and a system for direct deploy of static content. Static content is received at a deployment framework of an application server. The content is forwarded to a content deployment extension (CDE) for implementing the deployment of the content on the applications server. The application server operates in online mode during the deployment. The CDE selects an appropriate content handler to handle the deployment of the content. The content is deployed by the content handler on the application server in online mode. The CDE receive a feedback from the deployment of the static content.

Abstract: Methods and apparatus, including computer program products, implement a hierarchical arrangement of class loaders. Each class loader has a naming token, and each token driven class loader has one or more delegation tokens. A class definition request is received in a first, token driven class loader. If the first class loader has a parent class loader, the class definition is requested from the parent. If the parent is a token driven class loader, delegation tokens are used to delegate the class definition request to the parent. If the class definition is not obtained from a parent class loader, an attempt is made to obtain the class definition from the resources of the first class loader. If that also fails, the delegation tokens of the first class loader are used to find a matching child class loader and the class definition is requested from the matching child class loader.

Abstract: A system and method for integrating a diverse set of web/remote user interface technologies into one runtime architecture using a Web container extension is described. This integration simplifies execution, cross-usage, and technology integration between different user interface technologies and other application server offerings.

Abstract: A system and method for integrating a diverse set of web/remote user interface technologies into one runtime architecture using a Web container extension is described. This integration simplifies execution, cross-usage, and technology integration between different user interface technologies and other application server offerings.

Abstract: Methods and apparatus, including computer program products, implement a hierarchical arrangement of class loaders. Each class loader has a naming token, and each token driven class loader has one or more delegation tokens. A class definition request is received in a first, token driven class loader. If the first class loader has a parent class loader, the class definition is requested from the parent. If the parent is a token driven class loader, delegation tokens are used to delegate the class definition request to the parent. If the class definition is not obtained from a parent class loader, an attempt is made to obtain the class definition from the resources of the first class loader. If that also fails, the delegation tokens of the first class loader are used to find a matching child class loader and the class definition is requested from the matching child class loader.

Abstract: Methods and apparatus, including computer program products, implement a hierarchical arrangement of class loaders. Each class loader has a naming token, and each token driven class loader has one or more delegation tokens. A class definition request is received in a first, token driven class loader. If the first class loader has a parent class loader, the class definition is requested from the parent. If the parent is a token driven class loader, delegation tokens are used to delegate the class definition request to the parent. If the class definition is not obtained from a parent class loader, an attempt is made to obtain the class definition from the resources of the first class loader. If that also fails, the delegation tokens of the first class loader are used to find a matching child class loader and the class definition is requested from the matching child class loader.

Abstract: A method and system to provide easy access to factories in a naming service. The system receives an indication that a factory is needed by a client. A plurality of resolvers are checked in turn to find the factory indicated. If a resolver that can provide the factory is found, the factory is returned to the client. In one embodiment, resolvers register with a resolver manager that performs the checking in response to a naming operation. Because the resolver manager can access all registered resolvers, access to the factories is independent of a class path of the user.

Abstract: Methods and apparatus, including computer program products, implement a hierarchical arrangement of class loaders. Each class loader has a naming token, and each token driven class loader has one or more delegation tokens. A class definition request is received in a first, token driven class loader. If the first class loader has a parent class loader, the class definition is requested from the parent. If the parent is a token driven class loader, delegation tokens are used to delegate the class definition request to the parent. If the class definition is not obtained from a parent class loader, an attempt is made to obtain the class definition from the resources of the first class loader. If that also fails, the delegation tokens of the first class loader are used to find a matching child class loader and the class definition is requested from the matching child class loader.