"bill.burke(a)jboss.com" wrote : | addAllChildren isn't the way to go because the ear only deploys those things at the top level or those deployed in application.xml ... plus ... jars in the lib/ directory (for JPA). | | So, why did you remove the code in the old EarStructure code that I wrote that created DeploymentContexts? WHo is responsible for creating the deployment contexts in the EAR and determining their structure? | | I am really confused on WTF is going on. It was pretty clear before, but with this structure metadata it is not anymore... | | I said an addAllChildren that started at each file listed in the ear modules. The DeploymentContext is a mix of structure info and runtime metadata like the object models for ear descriptors. The StructureMetaData is to describe exactly what contexts in the vfs should be treated as deployment contexts, what the context classpaths are, and what the parent child relationships are. That is input to the MainDeployer to initiate the runtime deployment where the metadata can be obtained from the DeploymentContexts (created by the MainDeployer.StructureBuilder) using the associated virtual file and classpath info. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981148#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...