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.
We continue the cupcake success from the Milestone party in June. This time we go even bigger! A final release deserves a proper CAKE! Join us in the celebration, bake a cake, upload a photo of your creation and win big prizes!
The Jakarta EE Virtual Tour continues in 2021. Reach out if you would like us to visit your JUG/Meetup.
Are you still using JDK Internals? Well, then you should probably be aware that these will be encapsulated by default in Java 16. See JEP 396 for the details. Before you blow a fuse and start getting nightmares from your dependence on sun.misc.Unsafe, relax 🙂 It will still be available, at least for now. This applies to all the critical internal APIs for which standard replacements do not exist yet.
I think this lineup deserves some spotlight. JakartaOne Livestream 2020 is packed with quality content. Check out the schedule and make sure you register for the event!
Between the sessions, we return to Studio Jakarta EE where Tanja and I will talk about the sessions, celebrate the Jakarta EE 9 release, do some live demos, and interview community members. We will also feature a lighting talk by Amber Vanderburg where she will talk about the power of performance feedback. Make sure you tune in to these sessions between sessions. There will be some surprises coming up and, of course, there will be cake!
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 Jakarta EE 9 release will be properly celebrated with our JakartaOne Livestream on December 8. Make sure you register to save your spot! This will be a 12-hour event packed with amazing speakers and content!
Jakarta MVC 2.0 passed the plan review ballot this week. We have already done the work adjusting to the jakarta.mvc.* namespace and passed the TCK with Eclipse Krazo. The only thing left is to initiate the final steps for a Jakarta EE specification release, which we will do at the beginning of next week.
I want to thank everyone that voted in the 2020 JCP Executive Committee elections. The Eclipse Foundation keeps its elected seat and will continue to represent the interests of the open-source community there.
This is the last time I will be showing the status pie chart for Jakarta EE 9.
All the ongoing ballots will end this week, so the rest of the specifications are ready to be released on Friday.
This week, we visited NišJUG in Serbia on our Jakarta EE Virtual Tour. Next week, we travel across the Ocean to Philadelphia and PhillyJUG. Sign up for the event here.
The plan review for Jakarta MVC 2.0 is ongoing and we are in the middle of the work to finalize this version. One of the tasks is to pass the TCK with a compatible implementation. In our case, this is Eclipse Krazo.
Krazo supports runtimes based on Eclipse Jersey, RESTEasy, and Apache CXF. This means that it can be integrated into almost any Jakarta EE application server out there. For Jakarta MVC 1.1, we used WildFly 18 as our engine for running the TCK.
We already have the TCK passing on WildFly 22 (alpha), so we are actually good to go for starting a release review as soon as the ballot for the plan review closes (on November 19). That means that we have a couple of days to see if we can get it to run on other implementations as well. I’ll post a blog post later this week with a report on this work as a part of my series about the Jakarta EE Specification Process, featuring Jakarta MVC.
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.