On Sep 30, 2008, at 18:48, Johnston, Scott wrote:
Hi
We are upgrading an application from Java 1.4 to 1.5 that uses FOP
(v 0.93) (and subsequently an XSL transform). In the upgrade, the
FOP report fails with the following stack trace:
java.io.UTFDataFormatException: encoded string too long: 81879 bytes
at
java.io.DataOutputStream.writeUTF(DataOutputStream.java:347)
at
java.io.DataOutputStream.writeUTF(DataOutputStream.java:306)
at
com.sun.org.apache.bcel.internal.classfile.ConstantUtf8.dump
(ConstantUtf
8.java:121)
Seems like a limitation of Sun's DataOutputStream that Sun's internal
Xalan-fork does not take into account...
One thing to try, is to bypass the Xalan-version that is bundled with
Sun, and replace it either by the latest Xalan-release, or Saxon.
There are a number of ways to achieve this, either via Java System
Properties, or by means of the Java Endorsed Standard mechanism.
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
