...
The Geronimo Console is a web based way to deploy/start/stop applications, change JMS information etc. In addition to the Geronimo console, this could be some custom written tool, or some other J2EE management software. If a user wanted to stop an application using the Geronimo Console, the user would log into the web console and select the application to stop. When the action to stop the application occuredoccurred, the web console wouldn't access Tomcat directly. Instead the web console would query the kernel (through an MBeanServer) for the Tomcat GBean and then the kernel would reflectively execute the appropriate stop function in Tomcat. Note that this allows testing of the web console, the kernel and Tomcat separately from each other. All of the operations on the GBean occur via calls to an implementation of the Kernel interface allowing the implementation details of the kernel to change with minimal impact to the system. Behind the scenes, the BasicKernel class that implements the Kernel interface and employs the assitance assistance of many other classes. These other classes are all hidden behind the Kernel interface.
...
Name | Object Type | Description | ||
---|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="dc92ec98171fdc30-8fbc6a71-4aed4659-956bada5-a70b098b0bc4dc4192708492"><ac:plain-text-body><![CDATA[ | Abstract Name | AbstractName | Geronimo specific name of the object. It's a URI that uniquely identifies a given GBean. From the javadocs, it is defined by: [vendorId]/artifactId/[version]/[type]?key=value[,key=value][,...] | ]]></ac:plain-text-body></ac:structured-macro> |
Object Name | ObjectName | JMX name for a GBean. This is required by the JMX spec and would be used by JMX based tools to reference GBean objects | ||
Short Name | String | Will reference a GBean by name (a key/value pair of the Abstract Name) | ||
Type | Class | References based on type from the URI in the Abstract Name |
...