> As I said, the transformation
> works correctly it is just Process that refuses to terminate.
If you're using the incremental SAX2DTM features, it's possible that this
is related to a few very subtle glitch we discovered in how
CoroutineSAXParser was being used. The latest code is better in that
regard, but may not quite be perfect. I'm in the process of trying to
replace CoroutineSAXParser with a simpler API (IncrementalSAXSource), which
should eliminate the remaining hazard.
Can you try your test under a debugger, and determine which thread is left
frozen (and what it was doing at that time)?
