[XALANJ-1121] for-each trace events fired twice

• Type: Bug
• Status: Resolved
• Resolution: Won't Fix
• Affects Version/s: 2.4Dx
• Component/s: parse-or-compile, Xalan-interpretive
• Environment: Operating System: Linux; Platform: All
• Bugzilla Id: 11414
• Assignee: Unassigned
• Reporter: Tony Addyman
• Created: 02/Aug/02 21:04
• Updated: 16/Feb/11 23:01
• Resolved: 24/Sep/04 20:06

Description

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.