Apparently the dtd file specified in most configuration files (and the complete hibernate website) wasn't available this night for a couple of hours.

To make sure that in the future my programs that rely on hibernate don't crash (because of a timeout for the dtd), I would like to put the used dtd inside my jars.

But I've tried that before and failed. Just putting it in the jar and modifying the hibernate.cfg.xml to point to "hibernate-configuration-2.0.dtd" instead of "http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd" didn't cut it.

Anyone knows how to get it working?

Which hibernate version are you using? Ensure you're using the correct dtd for your version, as by default hibernate uses a customised entity resolver that looks in the classpath for the dtd first - this is why you'll find the dtd in the hibernate[2|3].jar

If you have any problems, there are many threads covering this subject already.

the dtd have always been inside hibernate.jar since the beginning of the project.

You could also try to set your xml parsers behaviour (in server-space) to non-validating, that would get rid of the problem altogether.

I had a struts app deployed on an oracle appserver (within an intranet without internet connectivity) and the app wouldn't boot because oracle's lame-ass xml parser lib would by default try to fetch any DTD

I know it's inside the hibernate jar, and that's exactly my problem.

Here is how it is written in chapter 1 of the Hibernate Reference Documentation:


So the hibernate2 jar is inside my classpath, but if the dtd on the web is not available for whatever reasons, no connections to the database can be established for new Configuration().configure(file)

Any way to disable this xml parsing for rich clients?

if you have the *correct* referenced DTD in your mapping files hibrenate will *not* try and connect externally to get it when parsing. Exactly as it states in the doc.