3 Replies Latest reply on Nov 28, 2006 7:12 AM by adrian.brock

    ServiceControllerMBean cleanup

    starksm64

      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.

        • 1. Re: ServiceControllerMBean cleanup
          starksm64

          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;
          }
          




          • 2. Re: ServiceControllerMBean cleanup
            weston.price

            Looks good. The new JCA stuff is going to need this. In fact, this was the original point of the task for programmatic deployment.

            • 3. Re: ServiceControllerMBean cleanup

               

              "scott.stark@jboss.org" wrote:

              Is there a point to keeping the org.jboss.test.system.controller.legacy as implementing ServiceControllerMBean?


              This is so the tests can be run twice (against old and new implementations)
              to avoid breaking backwards compatibility.