More info:
I found the following code near
org.apache.xalan.transformer.TransformerImpl line 3364:
catch (Exception e)
{
// e.printStackTrace();
if (null != m_transformThread)
postExceptionFromThread(e);
else
throw new RuntimeException(e.getMessage()); // Assume
we're on the main thread.
}
Among other things, this error check doesn't give enough info.
At the very least the e.printStackTrace() should be made operative.
So now I have to build my own Xalan-J just to get past this!
....
Of course, if anyone on the list has the answer to my question ...
well, I'll be a good citizen and report the flaws I find on Bugzilla
...
-----Forwarded Message-----
From: John Austin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Xalan issue in Cocoon java-util.EmptyStackException
Date: Mon, 20 Oct 2003 16:43:09 -0230
I posted the following on the Cocoon-users list and was directed
to this list as one of the local experts (J. Pietschmann) felt the
issue might be a recurrance of an old Xalan problem.
Does this item ring a bell here ?
<snip/>
--
John Austin <[EMAIL PROTECTED]>
--
John Austin <[EMAIL PROTECTED]>
