--- Scott M Stark <[EMAIL PROTECTED]>
wrote:
> > My problem is this:
> >
> > If I set them up to register with the JBoss
> MBeanServer, the
> > ServiceControlMBean receives notification of their
> registration and, in
> > spite of the fact that they do not implement
> org.jboss.util.Service,
> > calls init() on them unsuccessfully.
> >
> > It appears to me that:
> >
> > JBoss does not expect MBeans both not to implement
> Service not to be
> > statically loaded from a file.
> >
> > It seems to me that since I need to do exactly
> this with JettyJMX, that
> > we need to resolve this (apologies if there is
> already a way to do it
> > and I have missed it).
> >
> > Am I wrong ?
> >
> I believe so as JBoss expects that MBeans that needs
> lifecycle/dependency
> management do implement the Service interface
> methods, but if an MBean
> does not, it causes no harm. Are you seeing harm
> being done?
>
>
Yes.
The fact that JBoss calls init() on JettyMBeans
demonstrates that there is no way for an MBean to
indicate if it's lifecycle is or isn't managed by
JBoss.
This is an oversight.
What if JettyMBeans _HAD_ an init() method, that had
been called by Jetty already, JBoss would come along
and blindly call it again.
What if the init() method on a 3rd-party MBean had
nothing to do with lifecycle at all, but implemented
some entirely different feature known only to the
MBean creator and owner ?
Jules
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
>
http://lists.sourceforge.net/lists/listinfo/jboss-development
__________________________________________________
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
