You are viewing a plain text version of this content. The canonical link for it is here.

Posted to j-dev@xerces.apache.org by bu...@apache.org on 2004/03/10 23:08:45 UTC

DO NOT REPLY [Bug 27585] New: - DOMLocator.relatedNode returning null instead of problem node

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: xerces-j-dev@xml.apache.org
        ReportedBy: nnissar@ca.ibm.com


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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org