[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Duplicate DeploymentContext registration

[adrian@jboss.org]

"alesj" wrote : This eliminates the duplicates:
  | 

I found it very difficult to understand what the problem was from the forum threads
other than it produced a spurious warning, but I used your deployment structure to create a test that reproduced it and fixed the problem.

https://jira.jboss.org/jira/browse/JBDEPLOY-158

The issue was that both registerMBeans() from the top level deployment
and registerMBeans() from the subdeployment were trying to install the
sub-subdeployment mbean.

I've fixed it such that each mbean only recurses to one-level which is I think
what your fix was trying to do, but it wasn't very clean.

anonymous wrote : 
  | And another issue.
  | Isn't DeployersImpl::registerMBean called too early?
  | As at that point we don't have any components yet,
  | since the deployment hasn't gone yet through deployment stages.
  | It's just installed + manual mode --> Not_Installed state.
  | 

The idea is that the mbean is deployed as early as possible so you can analyse it
using JMX.
If you add/remove components or subdeployments later there are hooks to (un)register the mbeans.

I also started some much need missing tests to make sure this doesn't regress.

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

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