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
3. Extending the Administration Console
Administration Console Architecture
Implementing a Console Provider
About Administration Console Templates
Specifying the ID of an Add-On Component
Adding Functionality to the Administration Console
Adding a Node to the Navigation Tree
Creating a JavaServer Faces Page for Your Node
Creating JavaServer Faces Pages for Your Tabs
Adding a Task to the Common Tasks Page
Creating a JavaServer Faces Page for Your Task
Adding a Task Group to the Common Tasks Page
Creating a JavaServer Faces Page for Your Task Group
Creating a JavaServer Faces Page for Your Page Content
Adding a Page to the Administration Console
Adding Internationalization Support
Changing the Theme or Brand of 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
If your add-on component provides new content that you would like other people to extend, you may define your own integration point types. For example, if you add a new page that provides tabs of monitoring information, you might want to allow others to add their own tabs to complement your default tabs. This feature enables your page to behave like the existing Administration Console pages that you or others can extend.
The integration point type must be a unique identifier. You might use the package name of your integration point, with a meaningful name appended to the end, as in the following example:
org.company.project:myMonitoringTabs
Include code like the following below the place in your JavaServer Faces page where you would like to enable others to add their integration point implementations:
<event> <!afterCreate getUIComponent(clientId="clientId:of:root" component=>$attribute{rootComp}); includeIntegrations(type="org.company.project:myMonitoringTabs" root="#{rootComp}"); /> </event>
Change clientId:of:root to match the clientId of the outermost component in which you want others to be able to add their content (in this example, the tab set is the most likely choice). Also include your integration point ID in place of org.company.project:myMonitoringTabs. If you omit the root argument to includeIntegrations, all components on the entire page can be used for the parentId of the integration points.
Document the integration point only if your content is publicly available.
You or others can now provide an integration point that will be integrated into this page.
See Also
For more information, see the JSFTemplating API documentation.