The following comment has been added to this issue:
Author: Gianny DAMOUR
Created: Sat, 6 Sep 2003 8:39 PM
Body:
Please close this patch. It is by now no more in sync with the code base.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=GERONIMO-14
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-14
Summary: J2EEDomain, J2EEServer and JVM implementations
Type: Improvement
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: Apache Geronimo
Components:
management
Assignee:
Reporter: Gianny DAMOUR
Created: Sun, 24 Aug 2003 12:03 AM
Updated: Sun, 31 Aug 2003 7:39 PM
Description:
Implementation of the J2EEDomain, J2EEServer and JVM interfaces defined by
JSR77.
In order to implement this patch, I have updated some core components:
- AbstractComponent: this class extends now AbstractManagedObject and no more
AbstractStateManageable.
- AbstractContainer: the addComponent has been updated. The parameters provided
to the DependencyService.addStartDependency were not in the right order. More
accurately, the components contained by a container were not started when one
invoked startRecursive on the container.
- AbstractManagedObject: the class extends now Geronimo specific definitions of
the ManagedObject and StateManageable interfaces. These interfaces are
GeronimoManagedObject and GeronimoStateManageable. They have been defined
because it avoids to spoil the JSR77 interfaces with methods specific to our
implementation.
Moreover, the postRegiter has been implemented and declared as "final". A hook,
postRegisterHook, has been defined to provide to classes the ability to perform
post registration tasks. The postRegister method implements a mechanism used to
create JMX relations abstracting the relation of the JSR77 model.
For instance, J2EEDomain is related to one or more J2EEServer. When
a J2EEDomain is registered, postRegister retrieves, via getChildRelationTypes,
the types of the related managed objects, in this specific case the J2EEServer
type. A relation type having the name "J2EEDomain - J2EEServer" is then
created. A relation of this type and having the name "[j2ee domain
name]J2EEDomain - J2EEServer" is then added to the relation service.
When a J2EEServer related to the previous J2EEDomain is registered, it is added
to the "[j2ee domain name]J2EEDomain - J2EEServer" relation.
This relation is used to "implement" the method J2EEDomain.getServer.
I plan to use the same mechanism for all the managed objects covered by JSR77.
Cheers,
Gianny
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
