cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Upayavira ...@upaya.co.uk>
Subject Re: Cocoon hosting config hints
Date Tue, 08 Jun 2004 11:21:54 GMT
adrian.dimulescu@free.fr wrote:

> Upayavira wrote:
>
>> Basically, you've got to get Jetty (or tomcat) to mount the webapp 
>> without the /cocoon/. Then, you mount your app on /, so that 
>> http://localhost:8080/ is your application, so that:
>>
>> http://mycocoonhost/ maps to http://localhost:8080/
>
> Yes, that's what I thought. It's a pain though, I would have much 
> preferred that mod_proxy also rewrite the cookie path.

Yup. I'm sure there's a way - some Apache module somewhere. Just need to 
find it.

>> The more complex stuff I was talking about was how to manage more 
>> than one webapp mounted onto different domain names.
>
> AFAICS you won't be able to do that with cookie-based sessions just 
> because of that cookie problem : you only have one root webpath to map 
> to. Unless you mount every app in the root of its own domain name. 
> Which is just what you were saying in the last mail... Ok, it took a 
> while to get it :)

Good. Took me a while. A hack, but it works.

>> What servlet container are you using? Jetty or Tomcat?
>
> > Then we can look at how to reconfigure it to do that.
>
> I'm on Tomcat; no problem about reconfiguring things, thanks; it's 
> just that deploying a webapp in the webapps/ directory is so much 
> simpler.

Okay.

> What's with Jetty, I never tried it: is it simpler, is it faster or 
> what ?

Lighter, for me more reliable. Apparently  has a far lower memory 
footprint.

Regards, Upayavira



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message