"adrian(a)jboss.org" wrote : | You mean locally. That's two different questions depending on whether | it exports those resources/classes. | I also assume you mean a domain or the classloading system? | | There's a different question as to whether it can see it from one of its imports | or the domain if it is importAll. But that's just the standard classloading api. | It looks like ClassLoading is best point. "adrian(a)jboss.org" wrote : | 3. What are the classpath elements that are visible starting from a ClassLoader. Sort of a URLClassLoader.toURLs() view. | There's no such thing in general. If the policy is a VFSClassLoaderPolicy then you can ask what its VFS roots are and you could ask what other policies it can see that are VFSClassLoaderPolicys or URLClassLoaders. But the new classloading system has been designed to be flexible. There's no direct dependency of URLs/VFS etc. Somebody can implement a policy how they want. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123688#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...