Scoping of components while registering as MBeans

[jaikiran]

WRT https://jira.jboss.org/jira/browse/JBAS-6821, the MBeans corresponding to MC components are being registered in global scope. i.e. if two deployments with the same component name are deployed in the server then they will fail with InstanceAlreadyBoundException. Could the MBean name be changed to take into account the unit being deployed? i.e. scope it by including the unit name?

[jaikiran]

This piece in org.jboss.deployers.structure.spi.helpers.ComponentDeploymentContext

public ObjectName getObjectName()
 {
 if (objectName == null)
 {
 String name = getName();
 name = name.replace("\"", """);
 String temp = "jboss.deployment:id=\"" + name + "\",type=Component";
 try
 {
 objectName = new ObjectName(temp);
 }
 catch (MalformedObjectNameException e)
 {
 throw new RuntimeException("Error creating object name: " + temp, e);
 }
 }
 return objectName;
 }

[alesj]

Can you please create a Deployer JIRA and assign it to me?

[jaikiran]

Sure, https://jira.jboss.org/jira/browse/JBDEPLOY-184

[adrian.brock]

I'm assigning this JIRA issue back to Ales since I've got clue on what the problem is.

The component name represents a unique name within the MC. So unless
you're using a scoped kernel it isn't going to work anyway.

AFAIK, the deployers have not been updated to understand scoped kernels,
e.g. not just the name of the mbean but also checking "incomplete deployment", etc.

If the AFAIK is wrong, then I assume Ales knows how it works.

[jaikiran]

The component name represents a unique name within the MC.

Any specific reason why this is so? From what i read in the MC docs http://www.jboss.org/file-access/default/members/jbossmc/freezone/docs/2.0.x/userGuide/ch22s04.html, i was under the impression that components are scoped within deployment units:

"MC docs" wrote:
Components are never considered top-level deployments

Also, since the components are added/accessed within a DeploymentUnit (based on the DU.getComponent/DU.addComponent APIs), i thought the Deployers were responsible for ensuring that the component name is unique within that deployment unit, without having to worry about the uniqueness across deployment units.