I vote for Dave A. to do it, word is he just loooooves servlet containers! But really, it's pretty simple; the only problems I've experienced stem from the fact that configuration of Java servlet containers is somewhat non-intuitive (and I didn't know what I was doing). Experienced java admins have no problems accepting WO wars and deploying them.
- hugi On 22.7.2011, at 01:01, Pascal Robert wrote: > I think someone should do a podcast about deployment in servlet containers. > It's a topic that people talk about a couple of time per year but no example > or documentation in the wiki about it. > >> Hi Amy, >> You don't need "a full J2EE server" (whatever Oracle's decided that term >> means this week) to run WO apps — just the servlet container. >> >> And yes — running as a servlet, your timed tasks will run just as in a >> standalone application. >> >> I've deployed quite a few WO apps as servlets and it's easy — and sysadmins >> love it, since they know how to deploy wars, and it requires no addiional >> processes, plugins or configuration (beyond what's required for "standard" >> java webapps). >> >> Please don't hesitate to ask if you have problems. >> >> Cheers, >> - hugi >> >> >> >> >> On 21.7.2011, at 23:55, Emilian Bold wrote: >> >>> I'm no expert in WO deployment but I've recently tried something a bit more >>> complex than what you want (maven .war file generation for deployment) and >>> failed. It seems the WO community doesn't use Java containers very much. >>> >>> Now, from what I've read about WO, you should be able to run it in a normal >>> container as there is a dispatch WO servlet. I don't think you need a full >>> J2EE container, you should be ok with just a servlet container (but I'm >>> saying this just from reading the documentation, not experience). >>> >>> Regarding your timer, if you use WO I guess it could support that somehow >>> but a servlet is like a direct action -- it just responds to user >>> requests. Scheduling could be done via something as simple as crontab or >>> something heavy like Quartz (http://www.quartz-scheduler.org/ ); you might >>> also be able to spawn your own thread and do it manually but that's not >>> encouraged since the container is supposed to manage that. >>> >>> Anyhow, if you really want to stick with WO, the easiest way seems to be to >>> use what's tried and tested (wotaskd), otherwise you'll have your work cut >>> out for you just figuring you the integration part. >>> >>> --emi >>> >>> >>> On Thu, Jul 21, 2011 at 7:28 PM, Amy Worrall <amo...@gmail.com> wrote: >>> Hi all! >>> >>> I'm considering developing an app for a department at my university. >>> I'm talking to the university IT department about hosting it. In the >>> past I've only deployed on WebObjects itself, mostly on OSX Server, >>> but that's not going to happen here — anyhow, I don't know very much >>> about deploying Java stuff in general. >>> >>> I asked about Java hosting, and got this message back: >>> >>> "If you're looking for a servlet container (and not a full J2EE >>> server) and an RDBMS then there is a possibility that we'd be able to >>> provision you a Solaris 10 zone with Apache httpd and Tomcat on it. We >>> wouldn't put a database on here, but would typically make [space in] >>> an Oracle 10g schema (on a separate server) available." >>> >>> They also offered Windows IIS with SQL Server, or Linux with LAMP, but >>> he doesn't know whether they support Java on those platforms (said >>> he'd get back to me, and asked how firm a requirement Java was). >>> >>> Question is, what's the difference between a servlet container and a >>> full J2EE server? Would that option work for deploying WO stuff? Is >>> there anything I'd have to worry about when writing an app with WO to >>> deploy in that package? >>> >>> One thing I'd like the app to do is periodically (e.g. daily) download >>> a data feed from an external source. With a servlet deployment, my app >>> is still continually running so I can use a timer for such things, >>> right? >>> >>> Thanks, >>> >>> Amy >>> >>> -- >>> http://www.josekibold.ro : Honesty & well-done software. >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> http://lists.apple.com/mailman/options/webobjects-deploy/hugi%40karlmenn.is >>> >>> This email sent to h...@karlmenn.is >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/webobjects-deploy/probert%40macti.ca >> >> This email sent to prob...@macti.ca >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com
