DO NOT REPLY [Bug 18936] New: - Incremental mode: exceptions never posted to calling thread

[bu...@apache.org]

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

Incremental mode: exceptions never posted to calling thread

           Summary: Incremental mode: exceptions never posted to calling
                    thread
           Product: XalanJ2
           Version: 2.5Dx
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xalan.transformer
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: erik@bruchez.org
                CC: avernet@scdi.org,jmercay@scdi.org


In apache.xalan.transformer.TransformerImpl, method run(): the main work is done
in transformNode(m_doc). If an exception occurs in that method, its finally
block calls reset() on the TransformerImp, therefore setting m_transformThread
to null. In the following lines in run(), when the exception is catched,
m_transformThread is always null and postExceptionFromThread(e) is never called.

This means that in incremental mode, the calling thread is never notified of any
exception occurring when running a transformation.

A workaround is to remove the finally block in transformNode(), and to put try
{} finally {} blocks around the few calls to transformNode() in the code to do
the reset.

This being said, even after such change, calling postExceptionFromThread() does
not seem to work.