Jakarta MVC

To help you get to know the Jakarta MVC specification, here’s a recap of its history and status, and a brief introduction to the technology. Jakarta MVC History and Status The story of Jakarta MVC started back in 2014 when Java Specification Request (JSR) 371 was proposed in the Java...

This post concludes the mini-series about how Jakarta MVC 2.0 moves through the steps involved in the Jakarta EE Specification Process (JESP). All the posts are listed here, so bookmark this page for reference if you are involved in, or planning to be involved in a Jakarta EE specification. Jakarta...

Jakarta MVC 2.0 passed the release review ballot and is now ratified as a final specification according to the Jakarta EE Specification Process (JESP). The last steps for the project team after the ballot are to release the staged artifacts to Maven Central and verify that all published information is...

Before a Jakarta EE specification can be released under the Jakarta EE Specification Process (JESP), it has to go through a release review. The ballot for Jakarta MVC 2.0 can be followed in this ballot thread. The release review is initiated by creating a Pull Request to the Jakarta EE...

On Saturday, I will present Jakarta MVC 2.0 at the Kotlin Hyderabad Community. In this talk, I will go through a bit of the history behind Jakarta MVC, as well as showing it in practice. Be prepared for an intense Live Coding session! Jakarta MVC 2.0 is planned to be...

A specification must, according to the Jakarta EE Specification Process (JESP), provide a test suite to verify that an implementation implements the specification correctly. This test suite is called a Test Compatibility Kit (TCK). There must be at least one compatible implementation, i.e. an implementation that passes the TCK, for...

The work with Jakarta MVC 2.0 goes forward. According to the Jakarta EE Specification Process (JESP), we are now in the development phase where we will release as many milestones as we need until we are satisfied to move on to finalize the specification. There are already Milestone 1 releases...

We are ready to move forward with the namespace change from javax.mvc.* to jakarta.mvc.* for Jakarta MVC. This will be released as Jakarta MVC 2.0. According to the Jakarta EE Specification Process (JESP), we need to engage in a plan review with the Specification Committee. The key goal of this...