I had a similar problem using the XMLC (http://xmlc.enhydra.org/)
XML publishing framework. The only way I could find to solve this
was to either put the preferred parser in the CLASSPATH before
run.bat is executed, or to add the following line to run.bat:
set CLASSPATH=d:\java\xerces-1_2_3\xerces.jar;%CLASSPATH%
(the run.sh equivalent should be almost exactly the same, except for
using 'export', ':', and '$CLASSPATH')
before any other changes to CLASSPATH were made, particularly those
for Tomcat.
Hope this helps.
Chris
----- Original Message -----
From: "Anders Lindh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 08, 2001 2:13 PM
Subject: [jBoss-User] jboss, tomcat and cocoon
>
> Ok, guys, I need help..xs
>
> I've strugled a couple of days and now have jboss, tomcat
(embedded) and apache working together. What I still need, and can't
get working, is Cocoon. My configuration is: jboss PRE-2.1 (checked
out from cvs yesterday), Tomcat 3.2.1, Apache 1.3.14 and Cocoon 1.8.
Both jboss and Tomcat have been slightly hacked to enable apj13
communication with apache.
>
> The problem is Cocoon. It works with plain xml files, but xsp
files do not (for those who don't know what I'm talking about:
Cocoon processes xml/xslt files and has a xml based scripting
language called xsp. It compiles these on-demand to servlets and
thus allows creation of xml based web apps). Anyway, the error
messages are as follows:
>
> java.lang.NoSuchMethodError
> at
org.apache.cocoon.processor.xsp.language.java.XSPJavaPreprocessor.pr
ocess(XSPJavaPreprocessor.java:116)
> at
org.apache.cocoon.processor.xsp.language.java.XSPJavaPreprocessor.pr
ocess(XSPJavaPreprocessor.java:123)
> at
org.apache.cocoon.processor.xsp.language.java.XSPJavaPreprocessor.pr
eprocess(XSPJavaPreprocessor.java:81)
> at
org.apache.cocoon.processor.xsp.XSPLogicsheet.apply(XSPLogicsheet.ja
va:99)
> at
org.apache.cocoon.processor.xsp.XSPProcessor.process(XSPProcessor.ja
va:423)
> at org.apache.cocoon.Engine.handle(Engine.java:359)
> at org.apache.cocoon.Cocoon.service(Cocoon.java:167)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:
404)
> at org.apache.tomcat.core.Handler.service(Handler.java:286)
> at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:37
2)
> at
org.apache.tomcat.core.ContextManager.internalService(ContextManager
.java:797)
> at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:74
3)
> at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnecti
on(HttpConnectionHandler.java:210)
> at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:416)
> at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:498)
> at java.lang.Thread.run(Thread.java:484)
>
>
> Acording to all FAQ and posting I've read, this has to do with
Tomcat's classpath settings. If multiple xml processors are found
(or a DOM1 compliant is found before the required DOM2) error
reports should look like above. But I can't find a working
combination. I've tried tweaking jboss's run.sh to no avail. Has
anyone succeeded in getting Cocoon working with Tomcat and jboss?
What I'd like to know is what classpath does (embedded) Tomcat have
(and thus Cocoon)? Is it really the one specified in run.sh, or does
jboss do magic with the classpath before starting tomcat?
>
> Thanks,
>
> - Anders
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
