"scott.stark(a)jboss.org" wrote : "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. | Ok, i stepped through the CandidateVisitor code and it is making sense now. 1. I think there is a catch 22 in the current code. The CandidateVisitor will not determineStructure if the ContextInfo already exists in the StructureMetaData. StructureMetaData does not set the correct parent (and TreeSet order) until a parent has been added. Get me? 2. Since the EAR knows the structure of its subdeployments and what virtual files should be candidates, shouldn't it locate candidates and determine their structure rather than delegate it to addAllChildren method that curently exists? Are you finishing this code? I think I know what needs to be done now. Thanks for being patient. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981154#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...