"adrian(a)jboss.org" wrote : Do what you want, I'll fix it later. | This needs to work on the classpath notion. | | A visitor on the classpath (a concept that doesn't exist | but I suggested you write on an earlier thread) | should not be recursing into nested deployments. I'm fine with using DeploymentUnit.getDeploymentContext().getClassPath() as long as this classpath is equivalent to the notion of a resource loader in the old container. So for instance, a jar within a WAR would be its own DeploymentUnit with a context with a classpath of only that jar (and its manifest references). Bill View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976312#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...