I tried two things:
1) Adding the following into my Tomcat server.xml
<Context docBase="/opt/cocoon/build/webapp" path="cocoon"
debug="0" privileged="true"/>
But when I try to hit
http://localhost:8080/cocoon
I get a 404 error:
type Status report
message /cocoon
description The requested resource (/cocoon) is not available.
2) Copying /opt/cocoon/build/webapp to /opt/tomcat/webapps/cocoon
But when I tried starting tomcat in this manner it complains about XML
parsing stuff.
Jay
-----Original Message-----
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 4:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Session Lost between Tomcat and Cocoon
Ah, you even don't have Cocoon running in your Tomcat instance? Bad
Thing.
Jetty is not "under the hood". Jetty is the big thing, the servlet
container and Cocoon is deployed in it. The same can be done in Tomcat,
e.g. by setting a context in Tomcat's server.xml pointing to Cocoon's
webapp dir, copying this webapp dir to Tomcat's webapp dir and as third
doing "build war" and deploying the war into Tomcat.
Joerg
On 15.01.2004 00:38, Jay wrote:
> With Cocoon 2.1 it looks like they've intentionally separated
> themselves from Tomcat and have Jetty "under the hood". I didn't even
> see a way to run Cocoon inside of Tomcat as before.
>
> Jay
>
>
> -----Original Message-----
> From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 14, 2004 4:39 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Session Lost between Tomcat and Cocoon
>
>
> So you don't have your servlet connected to Cocooon, but you do an
> independent request from the client. Then it's obvious that the
session
> is lost.
>
> I'm not the servlet expert, but the sessions are managed by the
> container, aren't they? This means you can have the same session in
two
> servlets. And so you only have to add the sessionid to the your link
> when you call Cocoon:
>
> http://192.1.1.1:8888/proj/ReportT01.pdf;jsessionid=12345?clientId=10
>
> Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
