[ http://issues.apache.org/jira/browse/XERCESJ-1127?page=all ]
Michael Glavassevich resolved XERCESJ-1127:
-------------------------------------------
Resolution: Fixed
Fixed in SVN. The TreeWalker will now call isSameNode() if the DOM
implementation supports DOM Level 3 core (DOMImplementation.hasFeature("Core",
"3.0") == true). To minimize the performance impact on the common case, when
the DOM implementation is from Xerces the == operator is still used.
> TreeWalkerImpl - getNextSibling() implementation problem
> --------------------------------------------------------
>
> Key: XERCESJ-1127
> URL: http://issues.apache.org/jira/browse/XERCESJ-1127
> Project: Xerces2-J
> Type: Bug
> Components: DOM (Level 2 Traversal & Range)
> Versions: 2.7.1
> Environment: OS : Windows
> Reporter: Jérôme Candat
> Assignee: Michael Glavassevich
>
> Using a home-made DOM implementation, a problem has been raised while using
> the Xerces TreeWalker.
> One of our test consists in traversing the same XML file using Xerces alone
> and Xerces with our DOM implementation at the same time. Each result of the
> getNextSibling() method is compared to verify that the result is the same.
> In this test, we experienced a problem since we did not have the same
> results.
> I found the problem in the TreeWalkerImpl class at line 315. At this line two
> nodes are compared with the '==' operator. Though it works fine when using
> Xerces by itself, it does not work when another DOM implementation is used.
> By replacing this operator by the 'isSameNode' method, we obtain valid
> results.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
