"bill.burke(a)jboss.com" wrote : Come to think of it Classpath is more of an abstract thing. We need to know structure and deploy based on a structure. Which is exactly what the structure deployers do. They create the classpath from structure. Exists: Is this a jar? Well the classpath is the root Is this a war? Then the classpath is WEB-INF/classes and WEB-INF/lib/*.jar Doesn't exist: Is this a j2se system classloader, then the classpath is the paths from the system property. Or more likely each path element is made into a deployment unit so you could even add an ear to the classpath. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974898#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...