DeploymentInfo and DeploymentContext information

[vickyk]

I was under the impression that the DeploymentInfo would have been removed from the Jboss5 but it looks that it is still present there. I am not sure if VDF still need the DeploymentInfo , can you please provide some hint as where to find how the DeploymentInfo is populated in Jboss5 .
I was expecting the DeploymentContext replacing the DeploymentInfo but it seems that is not the case .

[starksm64]

The classes used and mentioned in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework is org.jboss.deployers.spi.deployer.DeploymentUnit. There is no use of DeploymentInfo by the new framework.

[vickyk]

Why is then system-jmx present in the trunk code?
https://svn.jboss.org/repos/jbossas/trunk/system-jmx/
This contains the ServerInfo class, also I saw some of the testsuite having this which created the confusion.

[vickyk]

I was looking at this jira
http://jira.jboss.com/jira/browse/JBAS-3411
This pointed to the org.jboss.test.deployers.ear.test.EARNoAppXmlDeploymentUnitTestCase where I could see the DeploymentInfo getting used .

[starksm64]

system-jmx contains both the old deployer classes and the new mc based deployers. The tests still need to be updated to the VDF.

[vickyk]

It looks that a DeploymentUnit(DU) contains multiple DeploymentContext(DC)
and each DC is linked to only one DU .
Considering the deployment as

A.sar(DC1)
-->B.sar(DC2)
---------->C.ear(DC3)
---------->D.ear(DC4)
--->E.ear(DC5)
---------->G.war(DC6)
----------->H.war(DC7)
---->I.jar(EJB) (DC8)

And all the DC's for a Tree which is represented by DU , this is logical relationship .
Is this how it goes ?

[bill.burke]

DU-DC is a one-to-one relationship. Not one-to-many.

The EJB Deployer only deals with DeploymentUnits.