One more comment appended to my last message. The problem is that (at
least in JRun) the server uses different Java class loaders for the
global classpath and each webapp context classpath. I'm guessing that
Cocoon must be loaded by the same class loader that loads xerces,
otherwise XSP compiling fails. The error you are seeing is very
misleading. It's the symptom of a problem, but not the root cause.
Dave
----- Original Message -----
From: "Dave Carlson" <[EMAIL PROTECTED]>
To: "JetSpeed" <[EMAIL PROTECTED]>
Sent: Thursday, September 28, 2000 8:13 PM
Subject: Re: Cannot compile portlets
> I had this same error, but managed to fix it. Now, if I can only
> recall exactly what I did that fixed this error...
>
> I am running Jetspeed 1.2b1 under the JRun 3.0 servlet engine, and
> initially tried to put the xerces.jar file into the server's global
> classpath (ahead of the old DOM libraries). I placed the remaining
> Turbine, Cocoon, etc. jar files into the servlet context lib path.
I
> believe that configuration produced the error you are seeing. I
then
> placed *all* jar files into the server global classpath, ahead of
all
> other jar files. This works.
>
> Unfortunately, if I want to create two instances of Jetspeed on the
> same server, I now have to create two entire JRun server instances,
> each with one Jetspeed context that has the jar files in the global
> server classpath. I've done this, and it works, but is more
resource
> intensive.
>
> Hope this helps!
>
> Dave
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
