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 validates the same XML three times against three different XSD, which are basically the same but with a growing severity ; each one contains more checks than the previous. The last XSD contains validations that are functionnaly only considered warnings for our application, and that's where foreign keys lie. The warnings can be ignored to process the step anyway, but it's definitely not identical to the user if there's one warning or one hundred. And in that case I would be glad that it's unpleasant to see ! I'll check the other answer, thank you again. 2010/5/21 Mukul Gandhi <[email protected]> > 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 > validation success or failure (i.e, a kind of 'true' or 'false' > validation outcome) after a XML schema validation episode. How > validation error messages are constructed, and how much of error > reporting is performed by schema engines, is implementation dependent. > > In this particular case, reporting all instances of > identity-constraint violations may be a nice to have feature (but > IMHO, it's still debatable, whether this is a best design in this > case), but not doing so, doesn't make Xerces non-compliant to XSD spec > :) > > It seems to me, that seeing all of identity-constraint violations if > error instances are as less as 2-3, may be good to see. But if let's > say we make the error list unbounded, producing all the error > instances (imagine this list size to be say, 500!) could be unpleasant > to see. >
