Jules,
> --- Scott M Stark <[EMAIL PROTECTED]>
> wrote:
> > They can't create a wrapper because mbeans are being
> > created as a byproduct
> > of interaction with the Jetty JMX interface. This is
> > a generic issue with integrating
> > third party services that happen to be mbeans which
> > may be using the JMX bus
> > for whatever purpose. Its trivial to add a filter by
> > domain
> > that allows ServiceControl to not even attempt to
> > manage any mbeans in a given
> > domain. This does not break the JBoss management
> > model in any way that I see.
> > It simply adds the notion of non-service domains.
> >
>
> Yes !
>
> Thanks Scott,
>
> This is it.
>
> How you choose to differentiate between JBoss Service
> MBeans and 3rd party ones is what I think the
> discussion should hinge upon.
Ehm, maybe I'm missing something but why the Vlada's solution isn't OK ? IE
modify the ServiceControl JBoss' MBean to check if the MBean belongs to the
JBoss lifecycle:
if (registration_notification &&
registeredMBean instanceof org.jboss.utill.Service)
{
list.add(registeredMBean);
}
Simon
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
