« Return to Thread: switch from Jetty to Tomcat

Re: Re: switch from Jetty to Tomcat

by Richard Vowles :: Rate this Message:

Reply to Author | View in Thread

I think it is probably best to call a spade a spade here and not disguise it. This is a trade-off because SpringSource purchased G2One and is an up/downside (however you look at it) of the SS commitment to Tomcat. I no-longer have a problem with this, as long as I can use Jetty (I use mor.ph and GAE), I am happy with this tradeoff - and I think everyone else will accept it as well. The key thing to remember is  that this is going to be a new, as yet unreleased, embeddable version of Tomcat we are talking about, not the... other one.

But the fact is, no-one will be using this "embedded" version of Tomcat you are talking about when it gets released, it will be a new version and will come with its own problems (which of course will be solvable because so much Tomcat dev is done inside of SS).  Everyone will be working with previous releases of Tomcat, for which there is already a Tomcat plugin for those who wish to use it - there appears to be no "problem" to solve for Tomcat - it is clearly about SS having a clearly defined "stack". Furthermore as more and more cloud hosting providers are using Jetty and Jetty was pretty much neck and neck with Tomcat in deployments (in 2007 no less, Netcraft stats), with GAE added to it, I cannot see how the "more Tomcat" argument holds water. Tomcat has a bad reputation for being a difficult server to administer and use in a development sense, but I trust Greame when he says that people will be no worse off with it.

I think the concern comes from those who have had to use Tomcat in the past and moved to Jetty just to get away from the pain. With SS on the case, and a Jetty plugin, I think we can all get what we need to continue smooth development and they will smooth out problems quickly. 1.2 is supposed to be stability release as well :-)

Richard

On Tue, Jun 30, 2009 at 2:10 AM, Jeff Brown <jeff@...> wrote:


I don't think I see the downside.  Grails developers will have the
option to choose which container they want to be used by commands like
run-app, a choice they haven't been able to make in the past.  If
there are going to be choices, something needs to be the default and
since more of our users deploy to Tomcat than Jetty, Tomcat seems the
sensible default.  For anyone who wants to continue using Jetty, they
will be able to do that.  I don't think anyone is really giving
anything up but a lot of folks are getting something that they have
wanted.

This really should not present a problem for any projects.




--
---
Richard Vowles,
Talk to me about development in Grails, Groovy, Java and for the Blackberry
ph: +64275467747, linkedin, skype:rvowles
get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! - http://tinyurl.com/cmcceh
podcast: http://www.illegalargument.com

 « Return to Thread: switch from Jetty to Tomcat