Re: A WebObjects article on Appleinsider
Re: A WebObjects article on Appleinsider
- Subject: Re: A WebObjects article on Appleinsider
- From: Chuck Hill <email@hidden>
- Date: Wed, 8 Jul 2009 10:52:01 -0700
Hi Bill,
On Jul 8, 2009, at 10:16 AM, William Hatch wrote:
On Jul 8, 2009, at 12:01 PM, Chuck Hill wrote:
On Jul 8, 2009, at 5:46 AM, William Hatch wrote:
On Jul 8, 2009, at 7:04 AM, David Avendasora wrote:
Yeah, this is really good news. Now that WO releases won't be
tied to OS X and Xcode releases, I'm betting we'll see far more
frequent releases of updates to the frameworks.
seriously? I remember the exact inverse statements being made
when, only four-ish years ago, they tied WO's release schedule
back into the main development tools. I think it's good news, but
hopefully it means that they'll stop developing their unnecessary
deployment that virtually nobody uses
??? I'd guest that the majority of WO projects are deployed like
this. Servlet deployment is a distant second.
Definitely, and my point is/was that perhaps if there weren't
resources going into maintaining a deployment option that the rest
of the world doesn't really use or care about, maybe it would help
on what I would consider to be the more important aspect of WO, that
being as a development framework. And, also, if deploying war didn't
totally suck ass for the most part, perhaps others wouldn't be so
reticent and apprehensive about deploying WO. Seriously, the bottom
line is that problems deploying in a standard container like tomcat
are certainly not helping the cause any. I personally could
absolutely not care less about wotaskd and monitor, and given that
there's another option that's much more ubiquitous, I further
propose that the rest of us adopt the same attitude.
The rest of the world does not care about WO _or_ WO deployment. I've
always thought it was quite decent, give or take a few bugs in a few
versions. Sure, it is very sensitive to IP/DNS configuration and user
error but Tomcat et al deployment also has its sensitive areas. And
isn't deployment of multiple instances via Tomcat a lot more work? I
never deploy a single instance.
While I agree that Apple should focus on the core frameworks, I would
not like to see that happen as the result of having to use an inferior
deployment system. The only real advantage that I see for J2EE
container deployment is that you can give the war to a deployment
group who knows nothing about WO. For me, that is not a compelling
advantage in the majority of cases.
Chuck
and focus on the frameworks instead. I hate the thought of one
more minute going into maintaining wotaskd, monitor and everything
else that goes along with WebObjects as a stand alone application
server. They should have done it long ago, and in all honesty, we
should have been willing to let that go a long time ago, if it
would have helped with resources inside apple devoted to
developing WO.
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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