The biggest things you lose is the built in load balancing and the
javamonitor. You will need to spawn your own instances and load
balance them externally. Deployment turns into a single war file that
is easy to do. It is much easier to deploy a war versus setting up a
wo deployment.
The other big gain is support for non wo supported platforms like
Linux, solaris, and windows
Dov
Sent from my iPhone
On Feb 1, 2010, at 10:02 AM, "Hugi Thordarson" <h...@karlmenn.is> wrote:
Hi all!
Quick question.
We're currently running a WO deployment architecture (wotaskd and
JavaMonitor). Some of our developers are adamant about switching to
using a servlet container for WO applications, specifically they
want to switch to Glassfish.
So, basically my questions are:
1) Is there anything gained by this change?
2) Is there anything lost by this change?
3) Does anyone here have experience running WO on Glassfish?
3) To sum it up: Should I care?
Cheers,
- hugi _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/drosenberg%40inquira.com
This email sent to drosenb...@inquira.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
