Abstract: A Java-based application server supports runtime operations of components that belong to multiple component models. The components may cross-reference each other. A component of a source component model can be integrated into a target component model to form an integrated component. State transitions of the integrated component can be managed according to the target component model with reference to the libraries of the source component model. The integrated component can be installed in the application server for execution by a Java virtual machine.

Abstract: A method and apparatus for using a microcontainer as a Plain-Old-Java-Object (POJO) based kernel in an application server. In one embodiment, the method includes dynamically construct deployed objects of a deployment from aspects. The method further includes providing a runtime infrastructure by dynamically constructing kernel objects of an application server from the aspects to execute the deployed objects.

Abstract: A Java-based application server, which supports multiple component models, includes a classloading module to enforce dependencies among classes and among the components that uses the classes. The classloading module determines whether a classloader created at deployment can share a version of a class with other classloaders. The classloading module also uses dependency information to determine which of the other classloaders on which the classloader depends. The classloading module uses pluggable classloading policies to determine the rules to be followed during classloading operations. The same state machine is used for classloading and for controlling the lifecycle of multiple component modules. The classloading module also utilizes abstraction of interfaces to communicate requirements and capabilities among the classloaders and with the system.

Abstract: A method and apparatus for providing a management interface to an application server to allow user access to managed properties of a deployment. In one embodiment, the method includes receiving metadata of a deployment describing managed properties, which are generated according to a user definition. The method further includes creating a management interface for the deployment to provide user access to the managed properties.

Abstract: A method and a system maintain a change to a component in an application server after the application server is re-started. The application server can be a Java-based application server that runs on a computer coupled to a management console. Through the management console, the application server receives an updated value of a component during runtime of the component. A profile service in the application server associates the component to a deployment descriptor that refers to an original value of the components. A representation of the component is then created and stored in a persistence data format in non-volatile data storage. The representation includes the updated value and indicates an association of the component with the deployment descriptor. When the application server is re-started, the representation is applied to the deployment descriptor to override the original value with the updated value.

Abstract: A method and apparatus for integrating aspect-oriented programming (AOP) into the deployment layer of an application server. In one embodiment, the method includes analyzing a structure of a deployment within an application server, and translating the deployment from a first form to a second form using results of the analyzing. The method further includes indicating in the deployment that a cross-cutting concern is to be resolved by aspects at runtime.

Abstract: A method and a system maintain a change to a component in an application server after the application server is re-started. The application server can be a Java-based application server that runs on a computer coupled to a management console. Through the management console, the application server receives an updated value of a component during runtime of the component. A profile service in the application server associates the component to a deployment descriptor that refers to an original value of the components. A representation of the component is then created and stored in a persistence data format in non-volatile data storage. The representation includes the updated value and indicates an association of the component with the deployment descriptor. When the application server is re-started, the representation is applied to the deployment descriptor to override the original value with the updated value.

Abstract: A Java-based application server supports runtime operations of components that belong to multiple component models. The components may cross-reference each other. A component of a source component model can be integrated into a target component model to form an integrated component. State transitions of the integrated component can be managed according to the target component model with reference to the libraries of the source component model. The integrated component can be installed in the application server for execution by a Java virtual machine.

Abstract: A Java-based application server, which supports multiple component models, includes a classloading module to enforce dependencies among classes and among the components that uses the classes. The classloading module determines whether a classloader created at deployment can share a version of a class with other classloaders. The classloading module also uses dependency information to determine which of the other classloaders on which the classloader depends. The classloading module uses pluggable classloading policies to determine the rules to be followed during classloading operations. The same state machine is used for classloading and for controlling the lifecycle of multiple component modules. The classloading module also utilizes abstraction of interfaces to communicate requirements and capabilities among the classloaders and with the system.

Abstract: A method and apparatus for providing a profile service in an application server for deployment configuration. In one embodiment, the method of the profile service includes populating a repository with deployments of an application server. The method of the profile service further includes managing the lifecycles of the deployments, and determining objects to instantiate when the deployments start.

Abstract: A method and apparatus for providing a management interface to an application server to allow user access to managed properties of a deployment. In one embodiment, the method includes receiving metadata of a deployment describing managed properties, which are generated according to a user definition. The method further includes creating a management interface for the deployment to provide user access to the managed properties.

Abstract: A method and apparatus for using a microcontainer as a Plain-Old-Java-Object (POJO) based kernel in an application server. In one embodiment, the method includes dynamically construct deployed objects of a deployment from aspects. The method further includes providing a runtime infrastructure by dynamically constructing kernel objects of an application server from the aspects to execute the deployed objects.

Abstract: A method and apparatus for providing a profile service in an application server for deployment configuration. In one embodiment, the method of the profile service includes populating a repository with deployments of an application server. The method of the profile service further includes managing the lifecycles of the deployments, and determining objects to instantiate when the deployments start.

Abstract: A method and apparatus for integrating aspect-oriented programming (AOP) into the deployment layer of an application server. In one embodiment, the method includes analyzing a structure of a deployment within an application server, and translating the deployment from a first form to a second form using results of the analyzing. The method further includes indicating in the deployment that a cross-cutting concern is to be resolved by aspects at runtime.