Keeping up with Java EE 8
Things are starting to move fast in the Java EE 8 universe. We checked in to see what happened in the past month, just to make sure you didn’t miss anything important. The big news is the final release version for JSF 2.3 but that’s not all that happened in March!
As the days are getting longer and spring settles in, it’s good to take a moment and see what’s going on over in the Java EE 8 world. The big news for March was the final release version for JSF 2.3. However, that’s not the only thing that happened last month from Java EE 8!
JSF 2.3 was released last week. Despite the fact that this particular framework has been around since 2002, it’s still a useful and relevant tool for developers.
This version includes a number of improvements and refinements to bring JSF up to speed with Java EE 8 and other frameworks used today. As requested, this release is aligned better with Java EE 8 and CDI.
JSF 2.3 boasts new CDI alignment improvements. This means that many JSF artifacts can now be easily injected into EL expressions and Java classes. That means no need for more JSF Managed Bean annotations!
There’s no need for any more workarounds for the new Date-Time API. Thank goodness! The new release of JSF 2.3 has a conversion tag to support the new Date-Time types. That’s not the only useful enhancement available in the new release. These all make this old framework easier to work with and more flexible. Community input has been very important to the development process. Head on over the release notes and see for yourself!
Java EE 8 wants to hear from you!
The slate over at Java EE is never empty. JSON-P 1.1 (JSR 374) and CDI 2 (JSR 365) have both passed the Public Review Ballot. They’re in the Proposed Final Draft stage. So, if you have any problems with the proposed versions, speak now or forever hold your peace. These two are scheduled to be released sometime in July (maybe!). Still, I’d be quick about it.
There’s an Early Draft of the JAX-RS 2.1 EG (JSR 370) out. It covers two out of three of the big ticket changes, including SSE support and a Reactive Client API. Additionally, there’s also a discussion happening right now about the details for the third feature, Non Blocking IO support.
Also, the first Early Draft for the Java EE Security API EG (JSR 375) has been posted. Remember to read the drafts and provide your feedback in a timely manner for both the JAX-RS 2.1 and the Java EE Security API!
IBM has confirmed that they aren’t going to do a Maintenance Release of the Batch API (JSR 352) for Java EE 8. Ooof.
As always, we urge everyone to be a good community member and check in on the 3rd Adopt a JSR online meeting. The Java EE community needs everyone’s help to keep this ecosystem running smoothly.