The JCP people have spoken
Heather Van Cura took to Oracle’s official blog this September to confirm the unanimous approval of seven JSRs (Java Specification Requests) for Java EE, with 24 votes in total from the JCP Executive Committee. Now they’ve had the official stamp of approval, the JSRs are ready and waiting for Expert Group Nominations.
The requests in question are JSR 366 (Java Platform Enterprise Edition 8 (Java EE 8) Specification), JSR 367 (Java API for JSON Binding (JSON-B) , JSR 368 ( Java Message Service (JMS) 2.1) , JSR 369 ( Java Servlet 4.0) , JSR 370 ( Java API for RESTful Web Services (JAX-RS) 2.1), JSR 371 ( Model-View Controller (MVC) 1.0), and JSR 372 (JavaServer Faces (JSF) 2.3).
Most significant among these is JSR 366, which outlines the key features of JavaEE 8. The proposed main focus in this release will be in meeting the HTML5 and the emerging HTTP 2.0 standard, continuing JavaEE’s trajectory of increased API simplicity with each iteration. There will also be an emphasis on tailoring the platform to fit emerging technologies in the web space and cloud technology.
HTTP 2.0 is also the focus for JSR 369, which aims to “expose support for the upcoming IETF standard HTTP/2 to users of the Servlet API,” with a secondary target of refreshing the Servlet API, partially as a response to community input, but also to achieve compliance with new features in HTTP 1.1.
It’s expected that the aforementioned Java API for JSON Binding (JSR-367) and Model View Controller (MVC) (JSR-371) will also be included in this release, as well as the JSR JCache (JSR-107). The API for JSON Binding will build on the API for JSON Process to provide for mapping between JSON text and Java objects, and the Model View Controller JSR will allow for action action-based MVC, to complement the component-based approach of JSF. In turn, JCache will enable scaling of apps by standardizing a universally accessible caching layer.
JSRs 368, 370, and 372 all incorporate updates to existing features. With the JMS, (JSR 368) proposes a series of improvements to the Java API for tapping into enterprise messaging systems from Java programs in both Java EE and Java SE environments, centering on ease-of-use enhancements and a host of other general improvements and fixes.
In JSR 370, the objective is to add support for new technology Server-Sent Events (SSE), defined as part of the HTML5 set of recommendations for a client to receive auto-updates from a server via HTTP. And finally, JSR 372 is directed at upping the clarity of the existing JavaServer Faces (JSF) specification and introduce a small, targeted set of new features, also community led.
When David Delabasse posted an update to the Oracle blog in June, he wrote that the goal was to have the Java EE 8 specification finalized in the latter half of 2016. It’s worth bearing in mind that it’s still relatively early days for the update, with plenty of room for adjustments between JCPs and Expert Groups. For now, it’s best to consider any plans as preliminary – rest assured we’ll be sure to keep you posted on developments as they happen.
Image by Michael Allen Smith