I've noticed trouble using the


inside of a servlet container (e.g., Tomcat). Using a jar this way works fine for 2-tier apps: the file system resolves the resource request. The


works fine in either place. Digging into the source, I think I see why:

In net.sf.hibernate.cfg.Configuration there is a now-deprecated . Does anyone know why this was deprecated and (re-?)written to call the file-based addJar? The corresponding addResource(String path) is much more robust: converting the specifed path into an InputStream, which is supported by both the file system and servlet containers.

Since there is a JarInputStream in java.util.jar I am curious, as a Hibernate newbie, why that is not used in the implementation of the addJar(String path) method.

Thanks.

The problem is in the addJar(String resource) method of configuration. I found a way to override this method that works for jar files (or zip files for that matter) read from a stream and hence properly resolved regardless of whether inside a container or not.

Problem solved. If others are interested let me know and I'll post the code.