Exit Print View

Sun GlassFish Enterprise Server v3 Add-On Component Development Guide

  This Document Entire Library
Print View

Document Information

Preface

1.   Introduction to the Development Environment for Enterprise Server Add-On Components

Enterprise Server Modular Architecture and Add-On Components

OSGi Alliance Module Management Subsystem

Hundred-Kilobyte Kernel

Overview of the Development Process for an Add-On Component

Writing HK2 Components

Extending the Administration Console

Extending the asadmin Utility

Adding Container Capabilities

Packaging and Delivering an Add-On Component

2.  Writing HK2 Components

3.  Extending the Administration Console

4.  Extending the asadmin Utility

5.  Adding Container Capabilities

6.  Packaging, Integrating, and Delivering an Add-On Component

A.  Integration Point Reference

Index

OSGi Alliance Module Management Subsystem

To enable components to be added when required, Enterprise Server provides a lightweight and extensible kernel that uses the module management subsystem from the OSGi Alliance. Any Enterprise 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 Enterprise 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 Enterprise Server is the Apache Felix OSGi framework. However, the Enterprise Server kernel uses only the OSGi Service Platform Release 4 API. Therefore, Enterprise Server supports other OSGi module management subsystems that are compatible with the OSGi Service Platform Release 4 API.