Hi Daniel, Hello Xerces Core developers, > I guess we have exactly the samt problem.
Yes, I think so, too. > >Anyway, maybe some of the validation code of Xerces could be > improved to > >report wrong order of child elements before their parent is closed. > >This would reduce a lot of responsibility out of any SAX > handler code and I > >am not sure if all SAX writers are aware of this as I was > not for a long > >time. > > I too considered this, but I don't have time to modify the > code right now, so > I'll probably stick to my earlier solution. I was not aware > of the fact that > validation errors are reported when an element is closed and > it really gave me > some problems. My problem was a wrong order of allowed child elements, daniel has the problem of not allowed elements. In this case I think the exception reporting on an endElement call is really bad in an SAX interface, as an SAX handler writer has to memorize all elements and put them after an successful endElement call into the "real", "approved", internal structure. This increases the complexity of every SAX-handler implementation, which relies on validation. I highly recommend to change validation reporting in Xerces. regards, Robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]