I think this merits further investigation. Does JarInputStream even
cover all our cases? We have found that in some deployments on
non-compliant servers the URL we get converts to neither a File nor a
JarInputStream and we have to do some guessing when we look for
orm.xml. I have not had a chance to assess whether there is a chance
that in a compliant server (one where unlisted classes should be
included) that we will get a URL that corresponds neither to a Directory
nor a Jar file.
It is probably worth entering a bug so this can be investigated.