Porting from Jetty 345.x to Jetty 6
Jetty 6 represents a major refactoring of the Jetty code based and thus if you are coding to the Jetty APIs you can expect that some considerable reworking of your code will be required. However, if your code is mostly against the servlet specification or closely related to it, then little or no changes should be required and only configuration need be updated.
There have been two major changes in the architecture of Jetty 6, both intended to improve the modularity and allow interceptor style extension.
Merged HTTP Request API and Servlet Request API
In Jetty 5, there was an API for pure Jetty HTTP requests and responses. The Jetty requests and responses where wrapped by the ServletHandler to provide the Servlet API for requests and responses. This architecture allowed for handlers to be written without servlet dependencies. However, given the re-entrant nature of Request Dispatches and the increasing involvement of the servlet spec in all common handlers (resoures, security, etc.). This Jetty/Servlet duality became an unwanted complexity when extending the server.
In Jetty 6, all requests and responses are based on the Servlet APIs requests and responses. This imposes a 136k JAR dependency on all jetty runtimes, but allows for significant reduction in the Jetty jar itself, as a parallel API is not required and much complexity is removed. Importantly this does not mean that all request are servlet requests and must be delivered by servlets. It simply means that jetty reuses the Servlet API as its own API for
common methods such as getParameter(String),getOutputStream() and getQueryString().
All Servlet facility, such as contexts, session, security, filters and servlets themselves are options. Only when the appropriate handlers are configured will the relevant parts of the servlet request/response API be active. For example:
- Without a SessionHandler the getSession() will always return null.
- Without a ContextHandler the getContext() path will always return null and the complete URI path will be available via getPathInfo()
new package names.
Build and packaging