Why would it be preferred over Tomcat?
Is your experience with big or little companies? Internal or external (customer/public facing) systems?
+1
A:
I have seen Jetty used for production deployments for lightweight http servers for restful services. For simple servers that relay requests back to a service Jetty is often enough.
Michael Shopsin
2010-09-30 20:33:54
+1
A:
It is used quite often in embedded mode. If your server needs extra http component, you can just throw in Jetty, write few servlets, and you're done. Tomcat isn't/wasn't as good for embedding as Jetty is.
Peter Štibraný
2010-09-30 20:34:07
+3
A:
You could look at this page listing products that use Jetty.
One example you might (unknowingly) be familiar with is that the Eclipse IDE's help system uses Jetty.
Richard Fearn
2010-09-30 20:36:15
A:
We use Jetty for a production environment. Very small and easy to install.
Starkey
2010-09-30 20:44:00
+4
A:
Google App Engine for Java (GAE/J) uses Jetty as servlet container.
Pascal Thivent
2010-09-30 20:47:56
A:
Jetty is in a lot of production environments. It is very easy to install, configure and deploy on. No fluffy management stuff that gets in the way.
Steven
2010-09-30 23:21:37