Model-View-Controller or MVC is defined as “a software architectural pattern for implementing user interfaces. It divides a given software application into three interconnected parts, so as to separation internal representations of information from the ways that information is presented to or accepted from the user”. MVC is said to be the most commonly used pattern in Web framework particularly in HTML based applications, this became evident in the recent survey conducted by RebelLabs where Spring MVC topped the chart with 40% votes.
Due to MVC’s popularity and with the result of the latest Java EE survey, JSR 371 was born. JSR 371 aims to develop an MVC specification for Java EE, which is called MVC 1.0. Initially, MVC 1.0 is a part of JAX-RS, the proposal to create a separate JSR for MVC 1.0 was announced by Santiago Pericas-Geertsen last August 19. The leads for this JSR are Oracle’s Santiago Pericas-Geertsen, also a co-lead of JAX-RS Specification and Manfred Riem, also a JSF Specification’s co-lead.
According to the proposed specification, Web UI frameworks has two classifications: Action-based framework, where “HTTP requests are routed to controllers and turned into actions by application code” and Component-based framework, where “HTTP requests are grouped and typically handled by each component in an independent manner”. Rather than a replacement to component-based JSF, it is stated that JSR 371, an action-based framework, is a new method in building Web applications on Java SE 8 or higher platforms.
The following Java EE technologies were being considered as leverage in the development of MVC 1.0:
- Model part – CDI and Bean Validation
- View part – JSPs and Facelets
- Controller part – JAX-RS
Final Release for this JSR is expected on the third quarter of 2016. For updates and other information on MVC 1.0, https://mvc-spec.java.net will be used as project site, though currently it is still empty. You can also get updates by following the two leads on Twitter, @spericas and @mnriem.