Hi Eliot, Oxygen uses Xerces by default for validating XSD. Our used Xerces version is 2.9.1 and we have a lot of patches (as you probably already know). Our validation code is something like: XMLGrammarPreparser preparser = ...................... // parse the grammar... preparser.setErrorHandler(..............); preparser.preparseGrammar( XMLGrammarDescription.XML_SCHEMA, new XMLInputSource(null, systemID, null, reader, null)); We also have some parser options in the Oxygen Preferences->"XML / XML Parser" which are used to create the parser. So it's hard to say why this difference occurs, maybe one of our many Xerces patches is a fix for your particular situation... What error does your validation report? Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 3/29/2011 4:40 PM, Eliot Kimber wrote:
I have an XSD that Oxygen validates fine but my own Xerces-based validator chokes on. Since the client asserts that the schema is valid, I want to understand why I'm seeing a difference in validation results when I would have expected them to be the same.
Is my understanding correct that Oxygen uses Saxon EE to do schema validation rather than Xerces?
Cheers,
E.