Java EE 8 has had its release date pushed back from Q4 2016 (when it would have been in time for next year’s JavaOne San Francisco) to the first half of 2017. Unfortunately, Oracle have had to tack on a few extra months to mitigate “various latencies involved in launching expert groups” as well as the other demands on the time of individual specification leads involved in the release. Writing in the Aquarium blog, John Clingan reveals that the team  will now be working to update target dates for the JSRs nestled under the Java EE umbrella.

Current lead offering Java EE 7 didn’t have the smoothest path to release. Dogged by a series of production issues, the update finally went GA on June 16th 2013, following the finalisation of the JSR 342 specification on May 28, 2013. Although it brought a few big headlining features like WebSocket and Batch Applications for Java Platform 1.0, overall the reception has been fairly muted when you consider the widespread embrace of Java 8.

Around this time last year, a community survey revealed that 65% of users had yet to upgrade to the latest version of Oracle’s enterprise Java option. No doubt Oracle are hoping user adoption will follow a similar pattern to OpenJDK, with the bulk of those still tooling in 6 making a bunny hop to Java EE 8.

There’s been increasing scrutiny on Java EE 7 as vendors work to support legacy versions of the platform thanks to slow industry uptake. Just last week, a war of words erupted when Spring guy Juergen Hoeller blogged that “it is fair to say that Java EE 7 failed to enter the market as a platform overall.” Naturally, this went down like a soggy MacBook with the wider open source community, with C2B2 Consulting quick to rush to Java EE 7’s defence.

There is a silver lining in Java EE 8’s delay however. Fortunately for you, Clingan writes, it means bonus time to get involved in the pulling the final polished version of the platform together. Clingan recommends that interested parties track JSRs and provide feedback by viewing the individual JSR mailing lists, wikis, and download and try out early Java EE 8 reference implementation builds.  You can find out more about Adopt a JSR here – and we also recommend reading this helpful guide for how Java comes together.

 

Wait Time for Java EE 8 Extended

About The Author
- Editor of Voxxed.com, focusing on all things Java, JVM, cloud-y, methodical, future-fantastic, and everything in between. Got a piece of news, article or tutorial you'd like to share with your fellow Voxxians? Drop us a line at info@voxxed.com

1 Comment

  • Juergen Hoeller
    Reply

    Let me note that the quote above is taken out of context: In my blog post, I argued that individual specs such as JPA 2.1 and JSR-356 WebSockets have seen adoption in the meantime, even as feature packs for some of the major EE 6 based servers. This is also the difference to other surveys: It is by no means the same whether some EE 7 level specs got adopted or whether EE 7 as a platform overall succeeded in establishing itself as the new baseline for production scenarios. The latter is clearly not the case (yet).

    The C2B2 blog post misinterprets some of my statements as well which has largely been clarified with the author – Steve Millidge – in the meantime. Please see my original blog post (which hasn’t been linked to above, just selectively quoted) for a richer discussion, in particular with Steve himself.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>