cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Lancelle <>
Subject Re: Was great, now doom and gloom...
Date Sun, 02 Jul 2000 08:01:37 GMT
I've go tto get some sleep.

Problem solved. For some reason, I placed a copy of cocoon.jar and Tomcat servlet.jar under
$JAVA_HOME/jre/lib/ext. After removing from this directory (of course, installed under $TOMCAT_HOME/lib),
all worked fine again.

'The doom and gloom is gone, and now the light shines down!!!' (now all I have to do is write

Jon Lancelle

Jon Lancelle wrote:

> I just had Cocoon working great with Tomcat 3.1.
> Then did something...?? Wish I could remember..oh yeah, tried to build a
> cvs of ant...but didn't use the build.
> Now I get the following message whenever I try to access an xml file
> with Cocoon running:
>             Publishing Engine could not be initialized.
>     java.lang.RuntimeException:
>         Error creating org.apache.cocoon.parser.XercesParser: make sure
> the needed classes can be found in the classpath
> (org/xml/sax/ErrorHandler)
>     at org.apache.cocoon.framework.Manager.create(
>     at org.apache.cocoon.Engine.(
>     at org.apache.cocoon.Engine.getInstance(
>     at org.apache.cocoon.Cocoon.init(
>     at
> org.apache.tomcat.core.ServletWrapper.initServlet(
>     at
> org.apache.tomcat.core.ServletWrapper.handleRequest(
>     at
> org.apache.tomcat.core.ContextManager.service(
>     at
> org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(
>     at
>     at
> I have gone through the faqs and over the installation several times,
> with no results. In my context, I have modified web.xml to look for the
> file (I place it under before the great
> gloom). Also, when Tomcat starts up, the *.jar files build the path
> correctly, placing the Xerces jar before the xml jar. In fact, I tried
> removing the xml.jar file. Tomcat startup balks...must need it.
> Any ideas? Maybe reinstall?
> Thanks,
> Jon Lancelle
View raw message