Sorry to dive back into such an old issue, but I have to

I need to validate the thinking behind one of the tests that came about because of this issue (or at least the test links this issue in its @TestForIssue). Specially org.hibernate.test.annotations.xml.ejb3.NonExistentOrmVersionTest. What this test tries to do is to "pin" a orm.xml mapping to a particular version of the JPA XSD by using an explicit xsi:schemaLocation directive in the xml:

<entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                 xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm orm_1_0.xsd"
                 version="3.0">
    ...
</entity-mappings>

The test then expects a failure because version="3.0" is illegal in the referenced 1.0 XSD.

However, in the new XML handling I completely ignore both any explicit schemaLocation directive and any explicit version value (details at HHH-8893 if anyone is interested).

Long story short, I think the test is not valid and would like to remove it. Anyone disagree?

One thing I would still like to do with HHH-8893 is to enable an option for "strict" validation of the XML according to the JPA ORM XSD which would then look at the version and use the version-specific JPA ORM XSD. But low priority tbh.