My problem is that there is no way to have Hibernate not call setValidate(true) on the Dom4J SAXReader created in the org.hibernate.util.XMLHelper, line 39 which is needed to use the non-validating XML parser Piccolo.

To see the problem, get a system working with Xerces. Then download Piccolo from http://piccolo.sourceforge.net/index.html and add -Djavax.xml.parsers.SAXParserFactory=com.bluecast.xml.JAXPSAXParserFactory to your startup parameters.

I've patched the local copy of my source to set validation to false and am not seeing any negative impacts of this change.

Two questions:
1. Are there any negative side effects to this that I'm not seeing? Is validation required for some feature I'm not using?

2. What would be the Hibernate-appropriate way to pass the validation flag as a parameter? Seems like Configuration.setProperty would be the most approriate way. Any conventions on property names?


Thanks for your time,

Randy


Hibernate version: 3.0.5

Mapping documents: Any

Code between sessionFactory.openSession() and session.close(): Error occurs on configure, before openSession

Full stack trace of any exception that occurs:




Name and version of the database you are using: Any (seen with HSML and MySQL)

The generated SQL (show_sql=true): None.

Debug level Hibernate log excerpt:

hbm xml files might be screwed up and users would raise ununderstandable questions on the forum. The validation is left intentionaly

Hi,

I'm behind a proxy. Sax is trying to validate the hibernate config by downloading the dtd which fails.

It would be really interesting to disable the xml validation !!

Is there another way of make it work?

Thanks,

well you can define a proxy to the vm.
But I don't understand why your parser tries to access the internet. Hibernate preven that by defining a EntityREsolver which tries locally to look up hibernate dtd and schemas

http://java.sun.com/j2se/1.4.2/docs/guide/net/properties.html for info on how to define a proxy, but if you do that you're just being lazy.

Hibernate provides a custom EntityResolver in order to solve the issue of resolving the DTD without network access, but that doesn't do squat unless your parser actually supports custom EntityResolver objects.

The problem is with the parser you're using. Either use a different one, or upgrade the version of the one you're using.

In my case, I need Piccolo for performance reasons, but this lib replaces de jaxp. So I need some low level disabling option for xml parsing.

Please note the the error mentioned occurs even if you use a properties file instead the xml.

I'm using hibernate 3.6.2.Final.

Tx in advance