Another aspect that should be applied to the recognized classpath indepdendent of the structure deployer is the VFSUtils.addManifestLocations behavior. The base classpath should be augmented via classpath manifest after the structure is determined. What if the StructureDeployer is updated to support an explicit StructureMetaData notion: | public interface StructureDeployer | { | /** | * Determine the structure of a deployment | * | * @param context the context | * @return true when it is recongnised | */ | boolean determineStructure(DeploymentContext context, StructureMetaData); | ... | | public interface StructureMetaData | { | /** The paths of subdeployments relative to the root DeploymentContext */ | public String[] getDeploymentPaths(); | /** The paths of classpath entries relative to the root DeploymentContext */ | public String[] getClasspathFiles(); | } | and instead of the first structure deployer determining the structure, all deployers can interact to augment the StructureMetaData. Creating DeploymentContexts and filling out the classpath based on manifests, etc would be aspects of the MainDeployer rather than structural deployer behaviors. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977638#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...