not finding all bad data elements at once

2010-05-21 Thread Guillaume Deshors
Hi I am facing exactly the issue reported by this oxygen user : http://www.oxygenxml.com/forum/topic2869.html?sid=a4b044cdcc3c06ae07059f924156f6d3 When using several keyrefs causing errors, Xerces reports only the first and then gives up. I would really like to have Xerces report all foreign key

Re: not finding all bad data elements at once

2010-05-21 Thread Mukul Gandhi
Hi Guillaume, First of all, this implementation behavior could not be a bug with a XML Schema engine, as XSD specification doesn't recommend anything about details of the error reporting, upon XML Schema validation failure. To my opinion, at the least XSD implementations are expected to report

Re: not finding all bad data elements at once

2010-05-21 Thread Michael Glavassevich
Hi Guillaume, Which API are you using and did you register an error handler? The default error handler for a JAXP Validator is defined as:? class DraconianErrorHandler implements ErrorHandler { public void fatalError( SAXParseException e ) throws SAXException {? throw e; }

Re: not finding all bad data elements at once

2010-05-21 Thread Guillaume Deshors
Hi Mukul Thanks for your answer. Understand me correctly, I'm not reporting this as a possible bug ; this behavior is understandable but I hoped there would be a way to nevertheless get all occurrences of this error. In my case it is necessaray, let me explain why : the system we're building vali

Re: not finding all bad data elements at once

2010-05-21 Thread Guillaume Deshors
Hi Yes that's what I did, though it's not directly the class Validator class that's directly involved. I used a SAXParser on which I set a custom DefaultHandler, like this : SAXParserFactory spf = SAXParserFactory.newInstance(); spf.setNamespaceAware(true); spf

Re: not finding all bad data elements at once

2010-05-21 Thread Michael Glavassevich
You're right. Only one error message is reported. It's been a very long time (years) since I've looked at identity constraints in Xerces. Couldn't tell you why it was implemented that way but that seems to be the behaviour. It isn't wrong. Xerces would be producing the correct PSVI (i.e. same erro