What are the benefits of embedding jetty vs deploying your webapp(s) in jetty? If you are planning on deploying more than one web app, should you strictly stick with deploying a war file for each web app (as opposed to writing an embedded server which calls each web app)?
+3
A:
Embedding jetty is handy in two cases I'm familiar with:
JNI. It's a lot easier to make sure you've got the right things in the right class loader.
Development. It's much easier to fire up an embedded jetty in eclipse than to dance around with the eclipse web tools and deal with deployments and debugger attaching.
bmargulies
2010-03-03 02:27:32
+6
A:
i'd use jetty embedded when the goal is to create a standalone application in which jetty is just one of the components (for example in an osgi container). if you just want to deploy some war's then a default jetty installation seems more preferable. i don't think the choice depends on whether you plan to deploy more than one webapp. when you embed jetty you'll have to do the plumping yourselves in your code.
Stefan De Boey
2010-03-03 02:34:05
However, what are the areas when to use a Jetty webserver over a full blown Tomcat WebServer?
Franklin
2010-03-15 13:14:14
Jetty and tomcat are comparable in size and capabilities.
Thorbjørn Ravn Andersen
2010-04-17 08:43:39
+1
A:
Have a look at the Winstone servlet container which allows you to distribute a single WAR file as an executable jar as a supported use case. This is what Hudson does.
Thorbjørn Ravn Andersen
2010-04-08 12:04:23