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=10665>. 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=10665 can't traverse the nodeset returned by xalan:nodeset [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2002-07-10 23:09 ------- There is a known problem in 1.2 involving certain searches into an RTF. You could try to retrofit the fix, but it was fairly complicated, and it would be next to impossible to track all of the changes involved. However, using for-each, I don't think you'd see this problem. Remember that converting an RTF to a node-set gives you a node-set with one node in it. You need to select the children of the RTF to do anything with it if you're using for-each: <xsl:for-each select="xalan:nodeset($RTF)/node()"> </xsl:for-each> The documentation may be in error, although I don't recall that particular sample. I would encourage you to consider upgrading to 1.3, or even to the latest CVS code. 1.2 is very old and we never patch an old release. You might also consider reworking your stylesheet so you no longer need to use the nodeset() extension function. In your case, you may be able to use the document() function to get the nodes as a true node-set. See the following FAQ for more information: http://www.dpawson.co.uk/xsl/sect2/N4995.html
