I have two instances of Tomcat. One that has my development webapps and it
is Tomcat 4.0.3. Another is empty and it is 4.0.4-b3. I put the FopServlet
in the 4.0.4-b3 version and tested it out and it worked fine after some
problems were resolved. Now, I've simply moved it into the webapps for my
i had that same error once, and the only thing i did is delete the jars and
put them back and then restart the tomcat...
seems strange but that worked for me...
greetings
Jochen Maes
ICT Development
KBC Securities (kbcsecurities.com)
Havenlaan 12 Avenue du Port SIF 8683
B-1080 Brussels
Subject: Re: Problem with javax.xml.transform.Transformer
From: "Wim Sandra" <[EMAIL PROTECTED]>
===
I can process the first XSL-FO document. But the following XSL-FO documents
fail with the same error: ClassNotFound on javax.xml.transform.Transformer.
It seems -but I'm
IL PROTECTED]
> Subject: Problem with javax.xml.transform.Transformer
>
>
> I have two instances of Tomcat. One that has my development
> webapps and it
> is Tomcat 4.0.3. Another is empty and it is 4.0.4-b3. I put
> the FopServlet
> in the 4.0.4-b3 version and tested it
FOP Newsgroup (@Basebeans.com) wrote:
I can process the first XSL-FO document. But the following XSL-FO documents
fail with the same error: ClassNotFound on javax.xml.transform.Transformer.
It seems -but I'm not sure yet- that I only have this problem when I process
the following documents from a
J.Pietschmann wrote:
Tomcat 4.0.3 has problems with the classloader. If you have to
use it, move the FOP jars into the Tomcat lib directory.
It is recommended to upgrade to 4.0.4
btw, I'm also having this problem now :( My hosting has been upgraded
from tomcat3 to 4.03 and fop stuck. But symptoms
Oleg Tkachenko wrote:
btw, I'm also having this problem now :( My hosting has been upgraded
from tomcat3 to 4.03 and fop stuck. But symptoms are rather bizarre -
java.lang.NoClassDefFoundError: org/w3c/dom/svg/SVGDocument
at
com.multiconn.fop.TIFFRendererFactory.newTIFFRenderer(TIFFRendererFactor
J.Pietschmann wrote:
I belive the Tomcat site itself mentions it. Other than
that, read the installation instructions for Cocoon regarding
Tomcat 4.0.3 and the Cocoon FAQ. The generally recommended
workaround is to move everything into the Tomcat lib.
You are right, that's particular bug 6374,
htt