Newly published Java EE 8 JSR draft shines a light on path ahead
After extensive community surveying, the latest draft of the JSR for Java EE 8 reveals plans for improved managed bean modules and expanded cloud infrastructure.
DeMicheil’s notes that, for those who’ve been following the progress of the surveys to date, there will be few surprises on what made the final cut. As we’ve established, it’s a resounding “Yes” to web standards. Augmenting HTML5 support in Java EE 7, the next version of Enterprise Edition is designed to support server-sent events and improve Java APIs for WebSockets and JSON processing. It’s expected that the emerging HTTP 2.0 will also be supported in Java EE 8. Support for the JAX-RS action-based MVC is also under consideration.
As we’ve seen in the community voting, it will likely be three new JSRs that form the Java EE 8 platform:
JCache (JSR-107): New caching layer which is accessible from all containers.
Java API for JSON Binding (JSR no number): Building on the API for JSON Processing and allowing for mapping between JSON text and Java objects.
Java Configuration (No JSR-number): New mechanism for specifying, packetization and accessibility of configured resources and properties regardless of the application.
Also expected is a refurb of the managed bean model to make ease of use features that are currently available only to selected components available to all managed beans through the mechanisms provided by CDI. In particular, DeMichiel and Co. will consider enhancements for declarative security by means of CDI interceptors and for notifications for timed events by means of the CDI event and observer mechanism.
Finally, it looks like the current Java EE 7 cloud infrastructure is set to be expanded in version 8. On the tentative roadmap, there’s support for configuration of multiple tenants and stripped down and improved security configuration, as well as REST-based APIs for monitoring and management.
Following a somewhat muted reception for Java EE 7, which took a hit from the deferral of several key JSR features (including the long awaited JCache), Oracle will no doubt be hoping for a little bit more excitement around this release. Now that the JSR has been put together, the next steps will be to submit it to the JCP ahead of the JavaOne timeframe. Click here to read the draft in its entirety in the meantime.