Hi,

after an upgrade from xerces 2.9 to 2.11.0 I noticed a different behavior with a EntityResolver2 implementation.

If I parse an XML file with a schema defined with a relative systemId, Xerces always resolves the systemId to an absolute one. This is the behavior of the EntityResolver interface and should not be the same with EntityResolver2, where the implementation should resolve relative systemIds.

Should I file a bug for this? This is a rather urgent problem and I cannot move back to 2.9.0, as this version cannot validate MODS documents correctly.

regards

Thomas Scheffler

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org

Reply via email to