I'm having a problem where I deploy a directory to the kernel and a .jar in a nested directory isn't getting deployed: foo/lib/deployme.jar I'm created a deployment context with "foo" as the root. The structure code successfully processes the foo/ directory. Mainly because the JARStructure deployer has determined that "foo/" is a top level directory, and so, it must process the children. Now, when lib/ is processed, the JARStructure deployer determines it is neither a "archive" nor a top level directory, so it does not process lib's children. Why do we do this? I can think of one reason. Maybe we don't want to process every single entry of every Jar file? If that doesn't really matter we could move directory processing out of JARStructure and into FileStructure. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012704#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...