xml-xalan-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26661] - Search fail in tree with normalize-space function
Date Thu, 05 Feb 2004 18:02:56 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26661>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26661

Search fail in tree with normalize-space function

David_N_Bertoni@lotus.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From David_N_Bertoni@lotus.com  2004-02-05 18:02 -------
As I stated before, I tested your stylesheet with a number of processors, and 
they all produced the same result.  There is no bug here.

In the first case you think is bad, no nodes are selected.  The normalize-space
() function accept a string as a parameter, but you are passing a node-set.  
The standard XPath conversion is to take only the _first_ node of the node-set, 
in document order, and convert that to a string.  The result is another string 
that has been normalized.  In this case, the string value is "d1", and the 
comparison to the literal string 'e1' fails.  The second case is similar.

You seem to be assuming the call to normalize_space() using a node-set will 
somehow return multiple strings, and the = operator will use existential 
quantification and find that one of the strings matches the literal 
string 'e1'.  Although that is how the = operator works with a node-set, it 
does not work that way with a function that accepts a string and returns a 
string.

Mime
View raw message