Re: WO Deployment [was:A WebObjects article on Appleinsider]
Re: WO Deployment [was:A WebObjects article on Appleinsider]
- Subject: Re: WO Deployment [was:A WebObjects article on Appleinsider]
- From: Q <email@hidden>
- Date: Fri, 10 Jul 2009 11:47:40 +1000
On 10/07/2009, at 8:24 AM, Andrew Lindesay wrote:
WOA's would then be built into 'war' or 'servlet directories' to be
unpacked into a servlet container – Jetty, Tomcat,
WebSphere...etc... In order to produce framework jars, I have
extended the standard ant "Jar" task with some specific WebObjects
material to build WebObjects framework jars. The same sort of
approach could be taken for building WOA 'wars' -- extend the 'War'
task. I'm not sure about Maven (sorry Henrique and Lachlan!).
I know Jetty is pretty easy to work with, but to make things easier,
a "tiny little servletish container" (TLSC) (thanks Mike) could be
written which would wrap the WebObjects servlet and feed it with
requests through the standard servlet API's. I know Jetty is really
easy to use, but this TLSC would be just there to run the one
servlet rather than a bunch of servlets so it would retain the
spirit of one instance = one process and the dead simple
configuration that WebObjects has now. It would essentially also
mean that there is a high level of continuity with what most of us
are doing now as well.
Embedding jetty is a very interesting idea because it's actually a
pretty decent web server for serving static content and copes well
under heavy load. If you were to embed Jetty and then port the
WOAdaptor to Jetty as a plugin / filter / servlet (or whatever it
uses), you would have a "WOAdaptor/wotaskd" app to replace wotaskd,
(as in the diagram), but it could serve as both a front end / load
balancer replacement for apache or as a load balancer agent for apache
or some other web server (responding to WOAdaptor, mod_balancer and
whatever other protocols). This would make small deployments VERY easy
because you could replace apache completely, but traditional
deployments would continue to work as they have always done. You would
then have the option of using either mod_balancer, a WOAdaptor plugin
like mod_WebObjects (but not limited to apache), or go direct to the
"WOAdaptor/wotaskd" wo app for your front end.
As long as the development process remains pretty much the same ie,
you run directly from the "expanded" framework and have rapid
turnaround of changes I don't think it's really a big issue if the app
is actually run and deployed as an embedded servlet or as a WAR with
jar frameworks.
--
Seeya...Q
Quinton Dolan - email@hidden
Gold Coast, QLD, Australia (GMT+10)
Ph: +61 419 729 806
_______________________________________________
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