Greg has released JettyJMX, a packaged which
integrates with Jetty in order that all major
components of Jetty become MBeans.
I have been integrating this into jboss_jetty, so that
Jetty is now listed by the JMX agent as a collection
of services, all with published interfaces, instead of
one megalithic service.
I have a problem !
JBoss seems to expect MBeans registered with it's JMX
Server to support a JBoss-inspired life-cycle
init()/start()/stop()/destroy().
Jetty MBeans support a different lifecycle which has
no init() method.
Every time a Jetty MBean is registered, JBoss tries to
call it's init() method, resulting in an exception
being thrown from within JMX.
Maybe I am taking the wrong approach.
I would like internal Jetty services to be available
to JBoss users via JMX. However these internal
services should be managed by Jetty, not JBoss (I
don't expect someone else to come in and call
lifecycle methods on objects I own...)
Can this be done ?
Do I register Jetty MBeans against another JMX Server
? If so can I hook this into the main JBoss one ?
Should JBoss-Jetty actually be this JMX Server ?
How should we scope groups of nested services within
JBoss ?
That should do it !
Jules
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
