I know you can get line information from the XmlError, will this not work for you? What about getting the XmlCursor using the XmlError.getCursorLocation() or even XmlError.getObjectLocation()? I have had success with those in the past, is there something preventing you from using them? -Jacob Danner
On 5/8/07, Les Walker <[EMAIL PROTECTED]> wrote:
Our application invokes the validate method of XML object and saves the returned XmlError messages through an XmlOptions instance containing a collection. We need to be able to report back to the user a list of invalid nodes and attributes, but it seems the source XmlObject field in the XmlError is mostly left unset. We can walk the tree from the bottom up and derive a unique set of invalid elements by recursively invoking validate, but it seems there should be a better way to pinpoint the source of error in an instance. Is this a bug? intended behavior? any suggestions how this can be acheived? thanks for any and all assistance LW
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
