This works OK with the built-in processor but the variable is empty if I change the scenario and
use Xalan. Any ideas why this should be the case and suggested workarounds?
Subject:Behaviour difference between built-in and XalanJ Author:Tony Lavinio Date:01 Mar 2005 03:41 PM
Could you try with one of the other Java engines - say Saxon 6 or 8?
This could help us to determine whether the problem is specific to the
Java version or to Xalan-J itself.
Subject:Behaviour difference between built-in and XalanJ Author:Tony Lavinio Date:02 Mar 2005 12:46 PM Originally Posted: 02 Mar 2005 12:47 PM
Since we've established that it is most likely a JDK problem and not
a problem specific to Xalan-J or either of the Saxons, there are a
couple of alternatives.
1. If you are on JDK 1.4, you might try upgrading to 1.5. If that works,
please let us know!
2. You could write a custom URI resolver for Xalan-J that would connect
and authenticate.
You might be able to get some help on the Xalan-J mailing list at
xml.apache.org