So the dependency on DeploymentInfo would be dropped, and the following metadata based install methods exposed:
| public interface ServiceControllerExtMBean extends ServiceControllerMBean
| {
| public void install(ObjectName name, Object object) throws DeploymentException;
| public List<ObjectName> install(List<ServiceMetaData> metaDatas, ObjectName loaderName) throws DeploymentException;
| public ObjectName install(ServiceMetaData metaData, ObjectName loaderName) throws DeploymentException;
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989153#3989153
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989153
One of the issues we had on ConnectionFactories and HAs was the need of using a sequence ID (OID) on ConnectionFactories (ClientConnectionFactoryDelegate and its respective ServerEndpoint).
After a design session with Tim we decided to stop using OIDs on AOPDispatcher for ConnectionFactories.
Now a ConnectionFactory *need* to specify a ClientID on the MBean constructor and that will be used to register the factory on JMSDispatcher.
Also.. that will be an issue when a customer is upgrading his version.. A customer would need to define the ClientID or the ConnectionFactory won't work, but we will have an exception clearing that. We could take the action of using a sequence case clientID is null (something we will have to think about later).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989150#3989150
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989150
I would like to drop the DeploymentInfo references in the ServiceControllerMBean coming in via the validateDeploymentState(DeploymentInfo di, DeploymentState state) method, and expose the non-xml based install methods of org.jboss.system.ServiceController to allow testing of programatic construction of services.
Is there a point to keeping the org.jboss.test.system.controller.legacy as implementing ServiceControllerMBean? If there is the metadata based install methods can be added as a subinterface.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989140#3989140
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989140
Ok, thanks for the clarification.
Well, the RARDeployer doesn't use the old MBeans, it's the XSL and DS deployers and that's not going away anytime soon, at least until I start migrating things over to MC/AOP. The programmatic deployment stuff was supposed to be an interim step along the way but once I started really looking at it things were not as straightforward as I initially thought.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989139#3989139
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989139