On Sep 24, 2007, at 10:48, Michael Bruns wrote:
Hi
<snip />
It turned out that the bug I was facing was caused by an incorrect
handling
of streams (input and output streams).
In my case streams weren't the problem, but a NullPointerException
which
was caused by calling xsl:value-of on an empty element. Obviously this
hasn't got anything to do with FOP either, but I still don't know why
this exception is thrown. It hasn't been thrown before and it still
isn't thrown on some machines on which my application is run, so some
third-party library or a library from the JDK has to cause the
problem.
If the problem is, as you describe 'calling xsl:value-of on an empty
element', then the bug/issue is located in the XSLT processor that is
bundled with the JVM. (For Java 5 or later, IIC, this means Xalan
XSLTC.)
Your options
* either drop the Xalan-jar that is distributed with FOP in the %
JAVA_HOME%/lib/endorsed folder on the machine in question; as such it
will override the default, bootstrapped XSLT processor.
* or set the JAXP system property
javax.xml.transform.TransformerFactory to use Saxon
Note that the second option may not be sufficient to switch to a
different Xalan-version (since the class-names are the same, the
version bundled with the JVM will still be found first on the
classpath), but it should work for a different vendor.
HTH!
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
