Right now the JARStructure deployer is stumbling around in the dark trying to identify whatever gets passed to it. The two problems I am current seeing are: 1. Its traversing directories it should not, for example, a directory entry in a jar archive. 2. Its not traversing directories it should, for example, a child directory in top level deployment (jbossweb-tomcat6.deployer/jsf-libs). This might be conflicts in the deployment oriented VFS.isArchive attribute, isLeaf, or just bugs, but we need the ability to explicitly define what the structure of a deployment is in terms of deployment contexts and classpath entries via metadata. With such a notion the ear structure deployer would just be a deployer that obtained this metadata via alternate descriptors. The JARStructure deployer would just be java coded logic to produce this metadata. So basically and extension of the ear application.xml structural elements (module and lib dirs) is what I'm thinking of. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977614#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...