juglviv
A big day for Java EE – Java EE 8 is now officially launched as JSR 366 via the JCP process. As you might have expected the primary focus areas are HTTP 2/HTML 5 support, CDI/managed bean alignment, cloud support and Java SE alignment.
Here is some of the very high level content:
Web Standards
- HTTP 2
- Server-Sent Events (SSE)
- JSON binding
- Action oriented web framework to complement JSF
- More support for Hypermedia
- Enhancements to JSON-P, WebSocket and JAX-RS
Managed Bean/CDI Alignment
- CDI 2
- Container services such as EJB style declarative security and scheduling made available to managed beans/CDI generally
- MDB style CDI based declarative JMS message listeners
- Pruning some of the older EJB 2/CORBA APIs
- JAX-RS alignment with CDI
Cloud
- Configuration
- Multitenancy
- Simplified security
- REST APIs for management and monitoring
Java SE
- Taking advantage of features available such as repeating annotations, lambda expressions, the Date/Time API, type annotations, Completable Futures and so on.
This of course is just the high level initial plan and there will be many other changes included such as updates to JSF and JMS as well as the addition of JCache/data grids. Do make sure to check out the JSR page on jcp.org for details. Now is the time to start getting involved or at least begin to think about it.
Besides the platform JSR, a number of APIs targeted to Java EE 8 have also now been filed, each under their own JSR. Check out the details on each JSR page:
- CDI 2 (JSR 365)
- JSON-B (JSR 367)
- JMS 2.1 (JSR 368)
- Servlet 4 (JSR 369)
- JAX-RS 2.1 (JSR 370)
- MVC (JSR 371)
- JSF 2.3 (JSR 372)
More Java EE 8 JSRs will be soon to follow. As always we will keep you informed here as things move forward, so stay tuned and let us know what you think.
Original article: https://blogs.oracle.com/reza/
