[#XALANJ-2286] count function applied to union as test of node identity is broken

XalanJ2

count function applied to union as test of node identity is broken

Created: 29/Mar/06 05:34 AM Updated: 11/Dec/07 04:35 PM

Return to search

Component/s:

Xalan-interpretive

Affects Version/s:

2.7

Fix Version/s:

2.7.1

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~XALANJ-2390~~ count( $x |. ) != count( $x ) not working as expected

~~XALANJ-2324~~ XPath function last() gives wrong result when select has a predicate

Reference

This issue relates to:

~~XALANJ-2204~~ Function Count on variable modifies number of nodes in variable.

Resolution Date:

31/Oct/06 04:47 AM

Description

« Hide

Using "count(.|$foo) = 1", where $foo is a node set consisting of one node, to test for node identity appears to be broken with Xalan-J Interpretive; it's always returning the value two or three. It worked in Xalan-J 2.7.0.

See ~~XALANJ-2285~~ for a test case. That issue reports a bug in XSLTC with the same test case.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Kevin Cormier added a comment - 11/Oct/06 08:37 PM

I've found a fix for this issue. The clone() method in FilterExprWalker should call m_exprObj.clone() rather than m_exprObj.cloneWithReset().

This problem has been identified as the cause of ~~XALANJ-2324~~, and was originally introduced by the fix for ~~XALANJ-2204~~.

[ Permlink | « Hide ]

Brian Minchau added a comment - 31/Oct/06 04:47 AM

Henry,
~~XALANJ-2204~~ caused this regresssion, and that issue was re-worked, so please confirm that this problem is fixed. If not, then re-open this issue.

[ Permlink | « Hide ]

Henry Zongaro added a comment - 31/Oct/06 10:55 AM

I can confirm that the bug is fixed with the latest source in the repository. Thanks!

[ Permlink | « Hide ]

Brian Minchau added a comment - 31/Oct/06 05:38 PM

Henry Zongaro (the reporter) has confirmed that the bug is fixed, so I'm closing this resolved issue.

[ Permlink | « Hide ]

Brian Minchau added a comment - 11/Dec/07 04:35 PM

The fixed version is marked as 2.7.1.
The affecteced version was marked as 2.7.1, which is clearly wrong.
Changing the affected version to 2.7, which is better, though perhaps not fully accurate.