An Oracle blog about Java Technology

Java EE 8 - May recap

David Delabassee
Software Evangelist

Here is a short recap covering some recent Java EE 8 updates.

In May, JSON-P 1.1 (JSR 374) has passed its Final Approval Ballot. Next to this, CDI 2.0 (JSR 365) has also successfully passed the Final Approval Ballot. Given the importance of CDI across the Java EE platform, this is a key milestone towards Java EE 8!  Make sure to check this CDI 2 – Weld 3 Tour.

Last month, JSON-B (JSR 367) has entered in the Final Approval ballot period. In the meantime, you can get Yasson, the JSON-B Reference Implementation, here.

Servlet 4.0 (JSR 369) , JAX-RS 2.1 (JSR 370) and Bean Validation 2.0 (JSR 380) have all finished their Public Review in May and are now in the Public Review ballot period. In addition, the respective Spec Leads gave a status update on their JSRs to the JCP Executive Committee:

Finaly, it should be mentioned that Java EE 8 (JSR 366) has also entered in the Public Review Ballot period. 

Java EE Security API (JSR 375) is now in Public Review; this is clearly an important step for this new API. 

Progress is also being made on different specifications that will get a maintenance release for Java EE 8:

Overall, we can observe a steady progress towards the finalization of the different Java EE 8 specifications. Last month, 2 promoted builds of GF5 were released. The fact that those are the first post-Java.net builds explains their relatively limited scope (see here and here). A lot of work has been done in the new GlassFish build pipeline. Now that this effort is mostly done, it is fair to expect a boost on GF5 progress in the coming weeks. To conclude on the infrastructure front, we should mention that all the Java EE related discussions are now hosted on a new platform javaee.groups.io. So if you have done so yet, join the conversation!

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.