| Exit Print View | |
Sun GlassFish Enterprise Server v3 Add-On Component Development Guide |
|
|
|
1. Introduction to the Development Environment for Enterprise Server Add-On Components
3. Extending the Administration Console
4. Extending the asadmin Utility
Representing an asadmin Command as a Java Class
Specifying the Name of an asadmin Command
Ensuring That an AdminCommand Implementation Is Stateless
Example of Adding an asadmin Command
Adding Parameters to an asadmin Command
Representing a Parameter of an asadmin Command
Identifying a Parameter of an asadmin Command
Specifying Whether a Parameter Is an Option or an Operand
Specifying the Name of an Option
Specifying the Long Form of an Option Name
Specifying the Short Form of an Option Name
Specifying the Acceptable Values of a Parameter
Specifying the Default Value of a Parameter
Specifying Whether a Parameter Is Required or Optional
Example of Adding Parameters to an asadmin Command
Adding Message Text Strings to an asadmin Command
Enabling an asadmin Command to Run
Setting the Context of an asadmin Command
Changing the Brand in the Enterprise Server CLI
Examples of Extending the asadmin Utility
5. Adding Container Capabilities
6. Packaging, Integrating, and Delivering an Add-On Component
To enable multiple containers to be independently packaged and loaded, the administrative command infrastructure of Enterprise Server provides the following features:
Location independence. Administration commands can be loaded from any add-on component that is known to Enterprise Server.
Extensibility. Administrative commands that are available to Enterprise Server are discovered on demand and not obtained from a preset list of commands.
Support for the HK2 architecture. Commands can use injection to express their dependencies, and extraction to provide results to a user. For more information, see 
Chapter 2, Writing HK2 Components.
|
|