| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server 3.1 Add-On Component Development Guide |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle GlassFish Server 3.1 Add-On Component Development Guide |
1. Introduction to the Development Environment for GlassFish Server Add-On Components
GlassFish Server Modular Architecture and Add-On Components
Overview of the Development Process for an Add-On Component
Extending the Administration Console
Adding Monitoring Capabilities
Adding Configuration Data for a Component
Creating a Session Persistence Module
Packaging and Delivering an Add-On Component
3. Extending the Administration Console
4. Extending the asadmin Utility
5. Adding Monitoring Capabilities
6. Adding Configuration Data for a Component
7. Adding Container Capabilities
8. Creating a Session Persistence Module
9. Packaging, Integrating, and Delivering an Add-On Component
To enable components to be added when required, GlassFish Server provides a lightweight and extensible kernel that uses the module management subsystem from the OSGi Alliance. Any GlassFish Server component that plugs in to this kernel must be implemented as an OSGi bundle. To enable an add-on component to plug in to the GlassFish Server kernel in the same way as other components, package the component as an OSGi bundle. For more information, see Packaging an Add-On Component.
The default OSGi module management subsystem in GlassFish Server is the Apache Felix OSGi framework. However, the GlassFish Server kernel uses only the OSGi Service Platform Release 4 API. Therefore, GlassFish Server supports other OSGi module management subsystems that are compatible with the OSGi Service Platform Release 4 API.
|