JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1 Add-On Component Development Guide
search filter icon
search icon

Document Information

Preface

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

2.  Writing HK2 Components

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

A.  Integration Point Reference

Integration Point Attributes

org.glassfish.admingui:navNode Integration Point

org.glassfish.admingui:rightPanel Integration Point

org.glassfish.admingui:rightPanelTitle Integration Point

org.glassfish.admingui:serverInstTab Integration Point

org.glassfish.admingui:commonTask Integration Point

org.glassfish.admingui:configuration Integration Point

org.glassfish.admingui:resources Integration Point

org.glassfish.admingui:customtheme Integration Point

org.glassfish.admingui:masthead Integration Point

org.glassfish.admingui:loginimage Integration Point

org.glassfish.admingui:loginform Integration Point

org.glassfish.admingui:versioninfo Integration Point

Index

org.glassfish.admingui:commonTask Integration Point

Use an org.glassfish.admingui:commonTask integration point to place a new task or task group on the Common Tasks page of the Administration Console. Specify the attributes and their content as follows.

type

org.glassfish.admingui:commonTask

parentId

If you are adding a task group, the id value of the Common Tasks page, which is commonTasksSection.

If you are adding a single task, the id value of the task group that is the parent for this tab, such as deployment (for the Deployment group).

priority

A numeric value that specifies the relative ordering of the tab on the page, whether at the top level or under another tab.

content

A relative path to the JavaServer Faces page that contains the content to be integrated.

For examples, see Example 3-7 and Example 3-9.