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=11414>. 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=11414 for-each trace events fired twice [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-06-26 21:27 ------- After thinking about this one, there appears to be no better solution than the status quo -- the double events are required to distinguish between each iteration (without it, a for-each selecting an empty node would not fire any trace events whatsoever). This behaviour can be worked around, if necessary, in the logic of your trace listener. To be in line with this logic, I think xsl:if should fire trace events regardless of whether or not the expression evaluates true.
