THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Wiki Markup |
|---|
{scrollbar} |
Overview
This section discusses the Geronimo Kernel. Before getting into the higher level overview of the Geronimo architecture as a whole, it's important to understand the kernel. Through the kernel, GBeans in Geronimo can communicate with the management utilities while being loosely coupled and not tied to JMX. This loose coupling that the kernel provides also makes testing much easier, and allows dependency management and injection. The kernel keeps track of the various GBeans in the system along with the various dependencies, references to other GBeans, attributes and methods. Below is a high level overview of the Geronimo kernel:
...
Name | Object Type | Description | ||
|---|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7d9a150aa682ffa1-b7331506-44f44f5e-9419a3ab-72d6c6963eda4bbf4e2601b0"><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 |
...