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 11414] New: - for-each trace events fired twice
Date Fri, 02 Aug 2002 14:04:53 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=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

           Summary: for-each trace events fired twice
           Product: XalanJ2
           Version: 2.4Dx
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: org.apache.xalan.templates
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: A.M.Addyman@salford.ac.uk


Calls to      
transformer.getTraceManager().fireTraceEvent(this); and   
transformer.getTraceManager().fireTraceEndEvent(this);   
appear in both execute() and transformSelectedNodes().   
This results in duplicated events being fired at the start   
and end of "for-each". As a newcomer to Xalan source the   
correction isn't obvious - to me. The end event logic in   
transformSelectedNodes includes a call to   
transformer.setCurrentElement(null); as well as firing the   
end event. If you are interfacing a debugger to Xalan, as I 
am doing, this is a problem. "Normal" users are unlikely to 
notice this issue.

Mime
View raw message