Sun has submitted JSR-315, Java Servlet 3.0 Specification , to the Java Community Process. According to the JSR,
This JSR is to develop the next version of Java Servlets - Java Servlets 3.0 Specification. One of the goals for Java EE 6 is extensibility. Servlet 3.0 specification will work on extensibility / pluggability. Web framework pluggability will be a key driver of the Servlet 3.0 specification. As part of the revision for Java EE 6 we would like to revise the Servlet specification to support the Ease of Development (EoD) using the newer language features. Also along with EoD there have been requests for enhancements in other areas as well to support the modern next generation web application development. This JSR tries to highlight some of the features that we plan to target with the next revision of the servlet specification.
Proposal
- Web framework pluggability.
- Almost all of the Java based web frameworks build on top of servlets. Most web frameworks today plugin either through servlets or through web.xml. Annotations to define some of the servlets, listeners, filters will help in making this possible. Programatic access to web.xml and dynamic changes to configuration of a webapp are desired features. This JSR will aim to provide the ability to seamlessly plugin different web frameworks into web appplications.
- EOD
- Annotations - use of annotations for the declarative style of programming.
- As part of the EoD effort the goal is to have zero configuration for web applications. The deployment descriptors would be used to override configuration.
- Generics - Use generics in the API where possible.
- Use of other language enhancements where possible to improve the usability of the API.
- Async and Comet support
- Non-blocking input - The ability to receive data from a client without blocking if the data is slow arriving.
- Non-blocking output - The ability to send data to a client without blocking if the client or network is slow.
- Delay request handling - The comet style of Ajax web application can require that a request handling is delayed until either a timeout or an event has occurred. Delaying request handling is also useful if a remote/slow resource must be obtained before servicing the request or if access to a specific resource needs to be throttled to prevent too many simultaneous accesses.
- Delay response close - The comet style of Ajax web application can require that a response is held open to allow additional data to be sent when asynchronous events occur.
- Blocking - Non-blocking notification - The ability to notify push blocking or non-blocking events. Channels concept - The ability to subscribe to a channel and get asyncronous events from that channel. This implies being able to create, subscribe, unsubscribe and also apply some security restriction on who can join and who cannot.
- Security
- Ability to login / logout.
- Self registration.
- Alignment
- Alignment / requirements from REST JSR (JSR 311).
- Alignment / requirements from JSF 2.0 JSR.
- Misc
- Better welcome file support.
- ServletContextListener ordering.
- Container wide definition for init params.
- File upload - progress listener - where to store interim and final file.
- Clarifications of thread-safety issues.
Comments are due by July 2.