I have created a webapp to deploy my application using Java Web Start, and I'm using the standard JnlpDownloadServlet to provide different file versions. For instance, the JNLP file would reference entities.jar, but the physical file on the web server might be entities-1.0.2.jar. This is normally handled by the web start internals, but Hibernate attempts to access the JAR file directly (I think to find the entities), using the "original" JAR file name without a version.
I believe the problem is in org.hibernate.ejb.packaging.JarVisitorFactory, in the function getJarURLFromURLEntry. This method takes a "jar:" URL and extracts from it the embedded "http:" URL. However this http URL does not have the version number included. Presumably the protocol handler for the jar protocol handles this internally.
In an effort to clean up, in bulk, tickets that are most likely out of date, we're transitioning all ORM 3 tickets to an "Awaiting Test Case" state. Please see http://in.relation.to/Bloggers/HibernateORMJIRAPoliciesAndCleanUpTactics for more information.
If this is still a legitimate bug in ORM 4, please provide either a test case that reproduces it or enough detail (entities, mappings, snippets, etc.) to show that it still fails on 4. If nothing is received within 3 months or so, we'll be automatically closing them.
Bulk rejecting stale issues. If this is still a legitimate issue on ORM 4, feel free to comment and attach a test case. I'll address responses case-by-case. Thanks!