"jason.greene(a)jboss.com" wrote : "jason.greene(a)jboss.com" wrote : | | Which seems to indicate that Ales' consistent use of / on non-leaf urls is the correct approach. | It is within a consistent context like only the vfs using the URLs. The problem is taking a relative path out of the context in which it was originally found, and then simply using new URL(jar, path) where the jar path may or may not be a directory in the spec sense. In reality URL(jarParent, path) should always work as jarParent "should" always be a directory. For ears this always works as they have no manifest classpath notion. For wars its confusing because they can have a manifest classpath as well as nested jars. | | If we built the classpath based on the original context and propagated it with the file with the manifest we would be ok, but this requires non-jdk api usage. | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211246#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...