...
Below we have a high level view of the interactions between a new plugin and Pluto. This is essentially the 'plumbing' beneath the administration console.
Center |
---|
|
We have a WAR file containing portlet information and the definition of an Administration Console Extension (ACE) GBean on the left. The ACE GBean is the way in which we can invoke operations on Pluto (this will be covered shortly).
...
The first use case we will look at will also be used to describe the individual pieces that make administration console function.
Center |
---|
On the left, we begin with a simple Geronimo deployment plan, for example, geronimo-web.xml. This deployment plan is the same deployment plan included in any archive that you may wish to deploy into Geronimo. In this case, the deployment plan includes the definition for a special AdminConsoleExtensionGBean
. The specifics of what goes into an AdminConsoleExtensionGBean
will be described in more detail later.
...
A deployment plan may also include definitions for multiple AdminConsoleExtensionGBeans
. This means that a deployment plan, if it chooses to do so, may add as many pages to the console as it wants to.
Center |
---|
Removing pages (Figure 3) from the console follows a similar process. Because the AdminConsoleExtensionGBean
implements the GBeanLifecycle
, when the installed component is stopped, its AdminConsoleExtensionGBean
will also be stopped. When this happens, we once more ask the kernel for the PortalContainerServiceGBean
, which is used to call removePortlet
on Pluto through its API. From the view of the administration console, the user will see the page has disappeared from the navigation menu (Figure 4). If the user starts the component again, the dostart()
method of GBeanLifecycle
calls{{addPortlet()}} method on Pluto Container, and the administration console extension reappears on the navigation menu (Figure 5).
Center |
---|
Class/Dependency Structure
...
- Command Line:
Example:No Format deploy deploy c:/HelloWorldPortlet.war
- Using the Admin Console:
Center
Verifying installation
Go to http://localhost:8080/console/ to verify that the portlets were added to the correct page. (You may need to refresh the browser if you deployed the application from the command line.)
...