Thanks, Scott.
I doubt it does the trick generally for EJB, but it does the trick for our
app server :-)
EJB is unkind to threaded algorithms to the point that I see this as a major
hole in EJB, though I suppose you could hide this in a Connector and
potentially skirt some of the
In response to this I've created the following method in
org.apache.xalan.TransformerImpl:
/**
* Create a thread for the transform. This can be overridden by derived
* implementations to provide their own thread, for thread pooling and
the
* like.
*
* @return thread suitable
[EMAIL PROTECTED] wrote:
"Roytman, Alex" [EMAIL PROTECTED] wrote:
One part which is sensitive to thread origin in my opinion is Extensions
In extensions people can do all sorts of things.
Yep, I can see that. It sounds like we should at least provide a property
to turn off the
"Roytman, Alex" [EMAIL PROTECTED] wrote:
One part which is sensitive to thread origin in my opinion is Extensions
In extensions people can do all sorts of things.
Yep, I can see that. It sounds like we should at least provide a property
to turn off the threading, which we should probably do
