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 released later in December, so this talk is a preview of what’s coming.
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 a spec to be ratified as a final specification.
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 available of both the Spec+API and the TCK in Jakarta Staging in which the namespace switch from javax.mvc.* to jakarta.mvc.* is done. The ongoing work is to update Eclipse Krazo to the new namespace and pass the TCK.
I will use Jakarta MVC as an example for a specification going through the steps involved in the JESP and blog about it here. Follow the Jakarta MVC tag to get them all.