Hi, The EntityResolver does get called unless you turn the SCHEMA_FEATURE off (what I did for testing...).
But how do I turn a String like "file:///path/to/schema.xsd" into an InputSource? new InputSource(getClass().getResourceAsStream(systemId)); does not lead to the same validation result as if no EntityResolver was given for an invalid xml file. bye Thomas ________________________________________ Von: Papendieck, Thomas [[email protected]] Gesendet: Donnerstag, 11. August 2011 09:12 Bis: [email protected] Betreff: AW: xerces ignores reader.setProperty(SCHEMA_LOCATION_PROPERTY,"path/to/xsd") Hello, unfortunately John's Idea does not work because 'resolveEntity' is not called in my implementation. Where do I look next for a solution? > reader.setEntityResolver(new EntityResolver() { > > @Override > public InputSource resolveEntity(String publicId, String systemId) > throws SAXException, IOException { > InputSource result = null; > // result = get the file from disk or however you need to do > it (); > return result; > } >}); bye Thomas ________________________________________ Von: Newman, John W [[email protected]] Gesendet: Mittwoch, 10. August 2011 19:05 Bis: [email protected] Betreff: RE: xerces ignores reader.setProperty(SCHEMA_LOCATION_PROPERTY,"path/to/xsd") I believe so yes .. but I'm not 100% Fire that up in the debugger and see what you get. Or just add some log statements to see when it's getting called and what values you're getting for public id / system id -----Original Message----- From: Papendieck, Thomas [mailto:[email protected]] Sent: Wednesday, August 10, 2011 1:03 PM To: [email protected] Subject: AW: xerces ignores reader.setProperty(SCHEMA_LOCATION_PROPERTY,"path/to/xsd") Hello John, that was fast... ;o) > public InputSource resolveEntity(String publicId, String systemId) Am I right that 'systemId' is (in my case) the path to the xsd as found in the 'xsi:schemaLocation' attribute? bye Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
