"bill.burke(a)jboss.com" wrote : "scott.stark(a)jboss.org" wrote : I have always thought jar urls were fundamentally flawed since they never have dealt with nested jars, and mix content with another protocol. Its also not really a protocol issue. I would like jar urls to disappear and whether or not a file was a compressed archive be a detail of the VFS. | | | | That's great you want to do this, but various SPIs in JavaEE5 require passing valid URLs. I'm running into this problem right now with nested jars within an EAR. PU need to pass in URL of the persistence.xml file but it is fucked up URL: | | jar:file:/.../foo.ear!/ejb.jar/META-INF/persistence.xml | | URL handler tries to open ejb.jar/META-INF/persistence.xml as a JarEntry within foo.ear (which its not obviously) | | Are we going to do: | | vfs:file:/.../foo.ear/ejb.jar/META-INF/persistence.xml? | | Is this something I can work on please as it is blocking me. | | Thanks, | | Bill Its something you can work on now that the structural deployer related vfs issues have been done. Instead of going with another nested url syntax, we may want: vfs-file:/.../foo.ear/ejb.jar/META-INF/persistence.xml so that URL/URI accessors like getPath, getHost, etc. work. They don't work with opaque url syntaxes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979465#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...