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]
