DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27585>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27585 DOMLocator.relatedNode returning null instead of problem node Summary: DOMLocator.relatedNode returning null instead of problem node Product: Xerces2-J Version: 2.6.2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: DOM AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] DOM L3 Core states that the relatedNode method of DOMLocator interface returns 'The node this locator is pointing to, or null if no node is available.' We send null to reportDOMError for the value of the error location (relatedNode param), in cases where we run into a DOM L1 node or an invalid character in a node name, and it appears that we could send the problem node (though there may be reasons for currently sending null that I'm unaware of). Failing DOM test cases (documentnormalizedocument05 and 13, infoset06, wellformed01) expect the problem node to be returned rather than null. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
