I think this was previously mentioned here, but this is also the case with
WebLogic and JRun.
-Lou
"John Harpour" <[EMAIL PROTECTED]>@actrix.gen.nz on 10/09/2001 06:14:04 PM
Please respond to [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc:
Subject: Problem with Batik, Tomcat, and FOP combination
Hi
I would like to bring attention to an issue I have come across recently
that
doesn't seem to be specifically documented anywhere.
I am using Batik with Fop, being served from Tomcat to generate PDF
documents
on the fly with embedded SVG in them. I was having trouble with getting the
SVG to parse correctly, with the following error:
java.lang.NoSuchMethodError
at org.apache.fop.svg.SVGElement.init(SVGElement.java:194)
etc.
The problem is classpath settings.
It turns out that Tomcat uses it's own classpath settings first, then tacks
the system classpath on the end before executing.
The result is that it doesn't matter if you ensure the batik.jar file is
first
in the system classpath (as recommended), tomcat will still enstantiate the
wrong DOM Implementation causing any SVG content to crash the page.
The solution is to edit the Tomcat startup script to ensure it puts the
system
classpath on the command line first (with batik.jar the first one listed).
It
then works happily using the correct DOM implementation object for the job.
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
