"scott.stark(a)jboss.org" wrote : "bill.burke(a)jboss.com" wrote : | | What I meant was that a module within the EAR is not getting determineStructure called. I know this for a fact as I'm stepping through... | | | | Now where to put determineStructure? Within DefaultStructureBuilder? | | | | BTW, can you please explain what DefaultStructureBuilder is trying to accomplish? Specifically, what is going on with all the Classpath stuff? Specifically, I need to know if the Classpath will only contain the EJB jar and not other jars so that I can scan propertly for annotations. | | | | thanks | | Ok. Its up to a given structure deployer to call out to the input deployers (or use the AbstractStructureDeployer.addAllChildren) to recursively process contexts. Right now its a determined type of structure deployer that is only creating child ContextInfos for those modules explicitly listed. They can't have nested deployments. This will have to be changed because the EARStructure does not really know what each type of module is in terms of strucuture. We should be doing an allAllChildren starting with each declared module. | 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... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981146#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...