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 "Jérôme Candat (JIRA)" <xe...@xml.apache.org> on 2006/01/10 12:43:19 UTC
[jira] Created: (XERCESJ-1127) TreeWalkerImpl - getNextSibling()
implementation problem
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
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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Updated: (XERCESJ-1127) TreeWalkerImpl - getNextSibling()
implementation problem
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESJ-1127?page=all ]
Michael Glavassevich updated XERCESJ-1127:
------------------------------------------
Fix Version: 2.8.0
> 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
> Fix For: 2.8.0
>
> 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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Assigned: (XERCESJ-1127) TreeWalkerImpl - getNextSibling()
implementation problem
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESJ-1127?page=all ]
Michael Glavassevich reassigned XERCESJ-1127:
---------------------------------------------
Assign To: Michael Glavassevich
> 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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Resolved: (XERCESJ-1127) TreeWalkerImpl - getNextSibling()
implementation problem
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ 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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org