Java Servlet Deployment - To Embed or Not - Tomcat/Jetty?

Well I think there is no direct answer; I might not fully understand the ". Deb" part as I'm not a debian freak :) I prefer having an instance of tomcat with a number of configurations aka CATALINA_HOME folders where you may specify apps and ports running, so you can always have all your configs separately and change the tomcat instance if needed. Also, see related post: Jetty: To embed or not to embed?

The web container I've found easiest to embed in a jar file (and it is still a valid WAR too) is Winstone (winstone.sourceforge.net/). Jenkins - jenkins-ci.org/ - use this container so it has been pretty stress-tested. Note that it is Servlet 2.4 only.

I also was used to Tomcat, so in my new project I tried using Jetty to learn about it. In an enterprise environment (where you have production / testing / development servers) I would stick to Tomcat, mainly because it helps you in getting to separate code from configuration files (now I am working in setting the conf files in a separate jar, because that way when I move changes from testing to production they do not have to manually update the jars that I'll pass to sysadmin). Other issue is that it looks like that Jetty has changed ownership not so long ago, and looking for info often got me to the old version.

Apart from that, using Jetty is not that different from Tomcat; had to run a little through docs for finding where everything is, but structure is (as last what I have seen, I have not tried anything too complicated) more or less like Tomcat.

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.