Re: Publishing Engine could not be initialized.

[Christopher Painter-Wakefield]

I'm sorry, I don't know the source of your problem, but I can help a little
bit.  My setup is mostly like yours.

The symbolic links shouldn't be a problem (I assume you are on some kind of
*nix).  My setup uses symlinks as well, and I've done that successfully on
both Solaris and Linux.  When you start Tomcat, it usually shows its
classpath.  Is it showing the xalan_1_2_D02.jar as part of its classpath?

I think most people just dump their jars in the tomcat/lib directory, and
let tomcat add them to the classpath.  You can easily hack the tomcat.sh
script for more control, though.  Mine now reads its jars from a file.

It seems like I've read about problems with JDK 1.3.1 on the list (I have
JDK1.3.0).  I don't remember the details, but you might want to search the
archives.  Maybe it is related somehow.

-Christopher




Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:

Subject:  Publishing Engine could not be initialized.


> java.lang.RuntimeException: Error creating
org.apache.cocoon.transformer.XalanTransformer: make sure the needed
classes can be found in the classpath
> (org/apache/xalan/xpath/xml/XMLParserLiaison)
>

I'm trying to just set up Cocoon with Tomcat, no Apache yet.  I've
symlinked the
necessary .jar files to the Tomcat /lib directory reather than doing a copy
as per
README, could this be part of the problem?  I also noticed that the
xalan.jar that
comes from Sun is more recent than the one shipped with the Cocoon package.
I've
tried both, same problem.  Tomcat works fine.  Suggestions?

Thanks - Tod

---

java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
Java HotSpot(TM) Client VM (build 1.3.1-b24, mixed mode)

Cocoon-1.8
Tomcat 3.2.3





---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>