The Java EE 8 target release will be somewhere in first half of 2017. The following figure shows the improvements of Java EE from version to version over the years from Sun to Oracle.
management and deployment.
In Java EE 7 the HTML 5 apps actually implemented by using Java API for WebSocket, the JSON Processing API, and Servlet NIO.But in Java EE 8, Oracle plans to augment support for HTML5 apps by adding support for server-sent events, standardized binding between JSON text and Java objects, and improvements to the Java API for WebSocket and the Java API for JSON Processing. This is great news for Java EE developers.
Java EE 8 updated JSRs
| API | JSR |
| CDI 2.0 | JSR 365 |
| JAX-RS 2.1 | JSR 370 |
| Servlet 4.0 | JSR 369 |
| JSON-P 1.1 | JSR 374 |
| JMS 2.1 | JSR 368 |
| Java EE Management 2.0 | JSR 373 |
| JSF 2.3 | JSR 365 |
| MVC 1.0 | JSR 371 |
| Java API for WebSocket 1.1 | JSR 356 |
About MVC 1.0
Leverage existing Java EE technologies
Model part should leverage CDI and Bean Validation
View part should leverage existing view technologies like JSPs and Facelets
Controller could be either JAX-RS based, invent a new technology, or defined a technology-independent way of defining
Model-View-Controller, or MVC is a common pattern in developing web applications.
Model – refers the application’s data
View – application’s data presentation
Controller – responsible for managing input, updating models and producing output
The MVC 1.0 falls into the action-based MVC and it is not a replacement for component-based frameworks such as JavaServer Faces (JSF).
