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 they
> wouldn't get managed)
>
Not right now, but it would be trivial to add this feature at
ConfigurationService.
public void registerService(String objectName,String serviceFactory)
public void unregisterService(String objectName)
> 2. Can a service started through jboss.jcml not register with service
> control? I think yes, this is what the new attribute is for.
>
Actaully it seems no. Service will always have proxy, but methods
(start/stop) invoked on proxy will be missed.
> 3. What are the advantages of having a 3rd party (ConfigurationService)
> register the desire for lifecycle management through a non mbean
> notification procedure over having each mbean wanting lifecyle management
> try to find a manager through the mbean notification? I would think as
> far
> as changing code just modifying the ServiceMBeanSupport class to ask for
> management would make all existing jboss services work just as they do
> now.
For notification, you would have to have special Notification event
(instead of generic REGISTRATION_NOTIFICATION) published stating that mbean
whants to be managed, this could be added to ServiceMBeanSupport. 3party
Mbean knows how to publish this notification, and ServiceProxy (as now)
facades MBean with incompatible lifecycle interface.
That also seems to be a viable solution.
Vladimir
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
