Thanks for the help, I decided to keep using my own "error types", it
makes more sense when viewing the errors.
Best,
Yoann
On 4/5/10 12:38, Mukul Gandhi wrote:
I think, Xerces internally stores all error outcomes (for example, 4
errors it prints in this case), for a particular validation episode
and returns all these to the user. Which I think, is good in a way
because we know, what all things went wrong with a given validation
situation.
If designing an XSD enumeration suits your situation, and the error
message in this case, makes more sense for a given use-case, please
feel free to design an enumeration.
On Tue, May 4, 2010 at 3:25 PM, yoann moranville
<yoann.moranvi...@gmail.com> wrote:
I would rather have an error saying:
---
line 37, error: cvc-enumeration-valid: Value 'value3' is not
facet-valid with respect to enumeration '[value1, value2]'. It must be
a value from the enumeration.
---
(I get this using my own complexType errors. So something like this
would be nice - it is easier to understand than the first 4 errors.)
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-users-h...@xerces.apache.org
