Hi David
> Is there a link to the spec?
No, JSR-77 is not published right now. I will provide the docs from the
JSR-77 classes which should give you a hint how it works by the end
of the week.
> Does this mean that for every existing mbean (instance) in jboss, we will
> have an additional JSR-77 mbean? I imagine it is obvious if you know
> anything about how this works ;-) but why can't you have the existing
> (service(mbeans implement the appropriate jsr-77 interfaces?
JSR-77 does not provide interfaces but only a model and meta-model.
JSR-77 should be dynamic like JMS and therefore we don't have interfaces.
Every vendor can add their own stuff as long as the core is compatible.
Also a service does not map a JSR-77 mbean one to one. It can be that
a service maps to many JSR-77 mbeans or that many services map to one
JSR-77 mbean.
> Could describe the nature of the links a bit?
It is some sort of an ObjectName (code wise it is the same) from JMX
but it only points to another "ManagedObject".
> For instance, how would you navigate to
> --a rardeployment
>
> --the ServiceController
>
> --an ejb container
J2EEManagement: is a management domain
- many J2EEApplications
- many J2EEModules
- either WebModule
- many Servlets
- either EjbModule
- many EJBs
- either RarModule
etc.
> Any light you could shed would be most welcome
Unfortunately JSR-77 is not published publicly therefore I cannot give
you the spec. But have a look at the JavaDoc I add to the JBossMgt
project by the end of the week.
Andy
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
