[jboss-dev-forums] [Design the new POJO MicroContainer] - JBMICROCONT-181 & ManagedDeployments

[scott.stark@jboss.org]

I just checked in the current direction I'm heading in terms of updating the contract for deployer layer in terms of management views. The top level management view is a ManagedDeployment containing ManagedComponents. The role of the existing ManagedObject is not explicit in these views. Its more of an implementation detail around ManagedPropertys being connected to a DeploymentUnit metadata attachment instance. The existing DeployerClient.getManagedObjects methods should be dropped in favor of the new DeployerClient.getManagedDeployment method.

Likewise, the ManagedObjectCreator should be dropped in favor of the ManagedDeploymentCreator/ManagedComponentCreator interfaces. What I'm currently doing is working through the use cases the existing ProfileServiceUnitTestCase has as well as the "TODO JBMICROCONT-181 Critique" comment Adrian has in the ManagedObjectCreator. 

I believe that we will have a standard ManagedDeploymentCreator implementation that uses the org.jboss.managed.api.annotation.* annotations to build the ManagedDeployment/ManagedComponent instances by parsing the DeploymentUnit attachments to identify what makes up the management interface. I also see that this could be augmented by deployers providing ManagedComponentCreators to deal with component properties that cannot adequately be described via annotations.

Right now I'm working on creating a DeployerManagedDeploymentUnitTestCase that illustrates the logic for a datasource(s) type of deployment. Let me know if there is a big disconnect with the api I checked in and this direction.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067530#4067530

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067530