From: <sco...@jb...> - 2005-07-29 14:54:29
|
The lack of an instant reply does not neccessarily mean lack of interest. An interface is not necessarily needed, and in general is not useful as the service layer deals with mbeans, not instance implementation. It would be that the service exposed such an attribute on the mbean interface. The xmbean deployment already has similar notions for a service that wants to know its MBeanService and ObjectName without having to subclass ServiceMBeanSupport. This is handled via reflection rather than an interface contract as the xmbean container is driven by attributes on descriptor rather than interfaces on the pojo. However, I think this is better handled as an extended service lifecycle event such as init(DeploymentInfo). The DeploymentInfo could be made available to the ServiceController/ServiceConfigurator either explicitly, or via a MainDeployer query if its not already there. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887313#3887313 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887313 |