See the custom service via MBeans howto:
http://www.jboss.org/documentation/HTML/ch10s40.html
The ServiceControl MBean section talks about the init/start/stop/destroy
lifecycle methods used by JBoss services.
----- Original Message -----
From: "Julian Gosnell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 10, 2001 9:40 AM
Subject: Re: [JBoss-dev] Nested JMX Service Groups...??!
> It doesn't go anywhere in JBoss, because it is not
> part of it.
>
> JBoss kicks off a JettyService (this IS configured in
> jboss.conf and DOES comply with JBoss' lifecycle
> interface).
>
> JettyService kicks off a JettyMBean which subsequently
> kicks off e.g. HttpListeners, WebApplicationContexts
> etc which are all MBeans. All are part of the inner
> workings of Jetty and have nothing to do with JBoss,
> thus are NOT configured in any JBoss file.
>
> However, Seeing as Jetty is a Service running within
> JBoss they may be considered subcomponents of JBoss
> and it would therefore be nice to be able to reach
> them from the JMX Agent page, see what they are doing
> and alter settings on them if you so need.
>
> I'm sure that JMX does not mandate a particular
> lifecycle for MBeans, otherwise the Jetty MBeans would
> share it, so it must be JBoss doing this.
>
> So I guess the question is, without rewriting half of
> Jetty, how can I connect Jetty's
> non-JBoss-lifecycle-compliant beans into JBoss' JMX
> architecture ?
>
> Jules
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development