Jetty or Tomcat?

You can find a good comparaison on this website: Jetty vs Tomcat.

3 It should be noted that the comparison has been written by someone on the Jetty team, so bias is likely. – duffymo Jan 2 at 4:27.

Even if you develop with Tomcat and plan to deploy it in Jetty, you will still need to test your deployment.So I would say it's possible as long as you do your testing. But then why introduce this hassle? You're better off developing with Jetty then deploy to Jetty.

Or Tomcat then deploy to Tomcat.

I'd say this is the best answer. Why make your life more difficult. In the Army we had a saying, you train like you fight.

I think the same rule can apply here as well. – jmort253 Jan 2 at 4:30 From my understanding it is supposed to be all 'standards compliant' so code should be interchangeable between the two. I did note the advantage of Tomcat being supported by my IDE of choice.

– DasWood Jan 2 at 4:37.

Jetty has some advantages going for it: Jetty is a fully fledged webserver in itself, so there is no need to maintain an Apache frontend. In fact, in my experience using Apache in front of Jetty causes you to lose some advantages. Jetty has support for many different non-blocking IO methodologies, and integrates with toolkits like Dojo.

Jetty is the web container of choice for Google App Engine's Java SDK. Although this may not matter to you now, Google has made it clear who THEY support. Tends to be more on the cutting edge.

Support for Websockets is included. Jetty can be easily embedded in your applications. Disadvantages: Documentation can sometimes be a little lacking.

Professional support is available from Webtide.

That is cool. I thought Google App Engine was just for Python. – DasWood Jan 2 at 4:45 Nope, they released the Java SDK in mid-2009.

What's really cool about the Java SDK is that the JVM can act as an abstraction layer for just about any language, such as PHP. – jmort253 Jan 2 at 4:57.

Tomcat has these things going for it: Been around a very long time - well over ten years. Used to be the reference implementation for servlet/JSP engine. Good support by Apache.

Current with servlet 3.0/JSP 2.2 specs - up to version 7. X now. Used by JBOSS as their servlet/JSP engine.

I don't see any reason to switch between development and deployment.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.