First created in 1995, Jetty has benefitted from input from a vast user community and consistent and focused development by a stable core of lead developers.
There are many more examples of Jetty in action on the Jetty Powered Page that has selections from among the tens of thousands of production Jetty instances.
However, as Jetty aims to be as unobtrusive as possible, countless websites and products are based around Jetty, but Jetty is invisible!
Jetty can be used as:
· a stand-alone traditional web server for static and dynamic content
· a dynamic content server behind a dedicated HTTP server such as Apache using mod_proxy
· an embedded component within a java application
This flexibility means that Jetty can be encountered in a number of different contexts:
· shipped with products to provide out-of-the-box useability eg Tapestry, Liferay
· distributed on CDs with books to make examples and exercises ready-to-run
· incorporated into applications as a HTTP transport eg JXTA , MX4J
· integrated as a web container in JavaEE app servers eg Geronimo, JOnAS, JBoss, JFox included as a component of an application eg FishEye, Continuum, Maven
Here are some key features of "Jetty":
· Configuration is either by API or by xml file
· Xml file syntax is a straightforward mapping from the API operating on POJOs
· Default configuration files make Jetty useable out-of-the-box
· Minimal number of lines required to embed a Jetty instance
· Performance degrades gracefully under stress for high quality of service
· Working Within the framework of existing web specificiations, handle large user loads and long-lived sessions with continuations
· Integrations available to clustering options such as WADI and Terracotta
· Dependencies are kept to the absolute minimum
· The core is kept small with extra functionality in optional jars
· Scalability is a key concern
· Performance degrades gracefully under stress
· Usage of dependency injection and inversion of control patterns
· Jetty is architected for pluggability. The API allows different implementations of all of the principal Jetty components to be selected. At least one, but sometimes more, implementations of a component are always provided. However if these do not meet your needs, you are free to code your own using the interfaces and abstract classes as a basis. This means that Jetty can be easily customised to a particular application environment. This is particularly useful when Jetty is acting as the web container in a JavaEE server, as Jetty`s pluggability ensures a tight integration with a host container.
What`s New in This Release: [ read full changelog ]
· etty-7.0.1.v20091125 25 November 2009
· 274251 DefaultServlet supports exact match mode.
· 288401 HttpExchange.cancel() Method Unimplemented
· 289027 deobfuscate HttpClient SSL passwords
· 289265 Test harness for async input
· 289959 Improved ContextDeployer configuration
· 289960 start.jar assumes command line args are configs
· 291019 Fix default DEBUG option; "-D.DEBUG=true" now works
· 291340 Race condition in onException() notifications
· 291543 make bin/*.sh scripts executable in distribution
· 291589 Update jetty-rewrite demo
· 292642 Fix errors in embedded Jetty examples
· 292825 Continuations ISE rather than ignore bad transitions
· 292546 Proactively enforce HttpClient idle timeout
· 293222 Improved StatisticsHandler for async
· 293506 Unable to use jconsole with Jetty when running with security manager
· 293557 Add "jad" mime mapping
· 294154 Patched jetty-osgi
· 294224 HttpClient timeout setting has no effect when connecting to host
· 294345 Support for HTTP/301HTTP/302 response codes
· 294563 Initial websocket...
