DO NOT REPLY [Bug 24423] New: - Tracing event of start element done before startElement() but trace event of end done after endElement()

[bugzilla]

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=24423>.
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=24423

Tracing event of start element done before startElement() but trace event of end done 
after endElement()

           Summary: Tracing event of start element done before
                    startElement() but trace event of end done after
                    endElement()
           Product: XalanJ2
           Version: CurrentCVS
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Xalan
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


org.apache.xalan.templates.ElemLiteralResult.execute(TransformerImpl) does:
if (TransformerImpl.S_DEBUG)
            transformer.getTraceManager().fireTraceEvent(this);
in the right place (before the startElement() call on the rhandler.

But it does the
        if (TransformerImpl.S_DEBUG)
            transformer.getTraceManager().fireTraceEndEvent(this);
after the call:
        rhandler.endElement(getNamespace(), getLocalName(), getRawName());

To be consistent the fireTraceEndEvent() should be just before the 
rhandler.endElement(...) to be consistent with the startElement() tracing.