"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. The current EARStructure deployer creates a context for the ejb jar, and only includes the jars referenced by the module classpath manifest: | ContextInfoImpl moduleContext = new ContextInfoImpl(module.getPathName()); | metaData.addContext(moduleContext); | // Add the manifest locations | addClassPath(root, module, false, true, moduleContext); | to include the jar the call should be addClassPath(root, module, true, true, moduleContext). The ejb jar should be in its own classpath, while a war should not. DefaultStructureBuilder is a dumb mapping of what the structure deployers specified as the deployment in the StructureMetaData. It should not be doing anything else or else its overriding what the structure deployers indicated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981126#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...