It's really difficult to analyse a bug report without an example that we can run in the lab, to watch the actual failure happen -- or, at the very least, a full backtrace on the exception that shows what was happening at the time.
The message you've shown us is not a Xalan error, which makes it particularly hard to use as a diagnostic. It's coming from Jasper, whatever that is. Again, if you can "unwrap" that exception to show the full stack trace, we may be able to get some useful information out of it. But it'd be much easier if you can find a way to reproduce the failure without Jasper in the equation. Since you're complaining about the <x:transform> tag, and that isn't part of Xalan's environment, I presume it's something provided by Jasper. Are you absolutely sure that the malfunction is in fact ours rather than theirs? ______________________________________ Joe Kesselman / IBM Research
