--- 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.
Jules
> ----- Original Message -----
> From: "marc fleury" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Sent: Tuesday, April 10, 2001 8:17 PM
> Subject: RE: [JBoss-dev] Nested JMX Service
> Groups...??!
>
>
> > |The stack trace is coming from the Jetty
> ModelMBeanImpl class, not JBoss's
> > |ServiceControl. Although annoying, this is just a
> cosmetic
> > |exception. To clean
> > |this up we could add a notification filter
> attribute to the
> > |ServiceControl mbean
> >
> > Again, implement the empty wrapper, that you don't
> want to do anything about
> > the integration is your problem but we should not
> start breaking the
> > management model in JBoss because you decide to
> ignore it.
> >
> > marc
> >
>
>
>
> _______________________________________________
> 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
