Hey,
> 1. Can a service started later, after jboss.jcml is processed.. such as
> dynamically through the html interface, or by jetty's service starter
> mbean, get registered with the ServiceControl? so as for instance to have
> its shutdown managed. (jetty is a bad example, this all started so
Hi,
This looks pretty good to me and better than what was proposed before, and
I have a couple of questions, not having looked at the code yet.
1. Can a service started later, after jboss.jcml is processed.. such as
dynamically through the html interface, or by jetty's service starter
mbean, get
|Were talking about the org.jboss.util.Service interface still. All
|the SC does
|now is maintain an ordered list of Service instances and it invokes the
|init/start/stop/destory methods in the registration order on these
|as before.
|Now it is invoking through a Service interface rather than the
> |2. The org.jboss.configuration.ConfigurationService mbean now registers all
> |mbeans loaded from the jboss.jcml configuration file with the
> |ServiceControl mbean.
> |There is no requirement that an mbean implements the
> |org.jboss.util.Service interface.
>
> ... h you are saying t
|2. The org.jboss.configuration.ConfigurationService mbean now registers all
|mbeans loaded from the jboss.jcml configuration file with the
|ServiceControl mbean.
|There is no requirement that an mbean implements the
|org.jboss.util.Service interface.
... h you are saying that when some
After much talking by me and some listening, here is the solution were going
with that I believe addresses all issues and requires no changes to existing
services and configurations:
1. The org.jboss.util.ServiceControl mbean service no longer listens for
mbean registration events as the means fo
