Oracle filed the umbrella JSR for Java EE 7 last week, and the specification has now passed the initial review ballot stage. The overarching themes are emerging web technologies, cloud computing, and continued ease of use improvements including an overhaul to the JMS API. Elsewhere, JPA is scheduled to receive attention, and Oracle is talking about plans to revive the long dormant JCACHE JSR.
Some of the most significant enhancements in Java EE 6 have occurred in the web tier. The Servlet API, the basis of almost all Java web frameworks, sees improvements to extensibility and plugability, and gains standardised asynchronous support. In the first of two articles on the EE 6 web tier InfoQ takes a look at the Servlet 3.0 specification.
The Servlet 3.0 specification sparked considerable debate last year. We take a look at the proposed final draft to see how the issues have been resolved.
JSR-315 has produced a Public Review (PR) of the Servlet 3.0 specification, accompanied by a reference implementation in the GlassFish trunk. This release has resulted in a debate around the choices that the Expert Group (EG) has taken for the next generation Servlet APIs and the whole of the Java EE 6 platform.
The draft specification of JSR-315 (Servlet 3.0) is now available and introduces a number of new features including asynchronous/Comet support, security improvements, and other ease of development features such additional annotations and web.xml fragments. With some of the new features generating considerable debate, the expert group are actively seeking community feedback.
As we transition from a page based view of web application development to an Ajax style data based new server programming needs emerge. Gregg Wilkins, lead developer on the Jetty web container, has been examining the need for an Asynchronous Servlet API in a series of blog posts. This review has resulted in Gregg concluding that continuations are the best solution at the present time.
Jetty founder Greg Wilkins has blogged about the need for the Servlet spec to evolve into an asynchronous model in order to, among other things, deal with the new challenges brought on by Ajax. Greg proposes standardizing a coordinator which could be called by the container in response to asynchronous event and would coordinate the call of the synchronous service method.
