Re: Multiple instances of WOA's deployed as WAR's
Re: Multiple instances of WOA's deployed as WAR's
- Subject: Re: Multiple instances of WOA's deployed as WAR's
- From: David Avendasora <email@hidden>
- Date: Fri, 17 Apr 2009 06:19:56 -0400
On Apr 17, 2009, at 3:26 AM, Tonny Staunsbrink wrote:
Hello
A recent posting said that "war file deployment just works" (it's
not an exact quote, but that how i remember it).
Yeah, I think that was me. I should have said:
Simple, single instance servlet deployments just work. If you create a
basic app and select the servlet options, you'll get a WAR file you
can deploy to a servlet container without any additional work. It used
to be quite a bit of messing around just to get a working servlet build.
When you start talking more advanced things like multiple instances
and such, I think it is still very much a case of lots of things need
to be done. My servlet deployments are very simple so I have never
gone that extra mile.
Dave
I've considered deploying WOA's in servlet containers, but there a
few issues i just can't see how they will work
if I run deploy an app to a servlet container cluster.
1) The default session store is memory resident, does WOSession hook
into whatever session distribution i setup
for the containers?
2) The instance number. As far as i can see this property becomes
meaningless when running in servlet containers.
If the session can be distributed, this may not be an issue, but i
not....
Can help me answering these by sharing their experience with this or
link me in the right direction (before i go experiment with it)?
Cheers
Tonny
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden