Directly after GOTO Amsterdam 2023 ended, I headed to the IKEA offices in Amsterdam with Geertjan and Geerit to speak at the Amsterdam JUG. We had a great walk through Amsterdam with Geertjan as our tour guide.
The 60 to 70 attendees were served Swedish meatballs (we were hosted by IKEA after all) and three talks. Check out the detailed agenda at the Amsterdam JUG Meetup. The slides from my talk “From Spring Boot 2 to Spring Boot 3 – And What’s Jakarta EE Got To Do With It” are available here. We had some really good questions and discussions after the talks. If you are in the Amsterdam area, make sure to join the group and attend their events!
GOTO Amsterdam 2023 was a really great experience! It was my first time speaking at a GOTO conference. In addition to Amsterdam, the GOTO conferences are organized in Chicago, Aarhus, and Copenhagen.
The venue, Beurs van Berlage is absolutely stunning. And the food is in the top tier of conference food. Usually, not a very hard list to climb on, but GOTO Amsterdam is definitely among the best.
My talk about Jakarta EE 10 with an additional demo of how to cope with the javax.* to jakarta.* namespace change in Spring was well attended. Check out the slides here.
As always when I go to conferences, I bring my running shoes and invite everyone to join me for a morning run. This time was no exception. Holly and I did a 5K run along the streets of Amsterdam in the light drizzling rain. Holly forgot her socks, so luckily I brought her a pair.
Welcome to issue number one hundred and eighty-two of Hashtag Jakarta EE!
This week’s update on the current status of the plan reviews for specifications targeting Jakarta EE 11 shows that there are now three approved plans, four on ballot, and nine ready for ballot (Snapshot from Sunday, June 25, 2023):
On Ballot Jakarta Authentication 3.1 (ballot) Jakarta Expression Language 6.0 (ballot) Jakarta Pages 4.0 (ballot) Jakarta Persistence 3.2 (ballot)
Ready for Ballot Jakarta Authorization 3.0 Jakarta Concurrency 3.1 Jakarta Contexts and Dependency Injection 4.1 Jakarta Interceptors 2.2 Jakarta Faces 5.0 Jakarta Security 4.0 Jakarta Servlet 6.1 Jakarta WebSocket 2.2 Jakarta MVC 3.0
If you pay special attention, you will notice that the plan reviews for Jakarta Authentication 3.1, Jakarta Pages 4.0, and Jakarta Persistence 3.2 should have ended by now. Plan reviews have a 7-day voting period. However, a specification committee member can request to extend the period up to 30 days. That is what happened with these. They all have enough votes to be approved, but we are just waiting for the last votes to be able to close the ballot.
This week, the Eclipse Foundation staff met in Ottawa for our annual all-hands. We had a whole week of sessions, training, team building, and a whole lot of fun. In between the scheduled activities, we also had some opportunities to explore Canadian wildlife as seen in these pictures.
And, we are a sporty gang as well. On Thursday morning, a big bunch of us met up in the hotel lobby at 06.29 (that is AM) to go for a morning run.
Welcome to issue number one hundred and eighty-one of Hashtag Jakarta EE!
The scope of Jakarta EE 11 is taking shape. Here is an update on the current status of the plan reviews for specifications targeting Jakarta EE 11 (Snapshot from Sunday, June 18, 2023):
On Ballot Jakarta Authentication 3.1 (ballot) Jakarta Pages 4.0 (ballot) Jakarta Persistence 3.2 (ballot)
Ready for Ballot Jakarta Authorization 3.0 Jakarta Concurrency 3.1 Jakarta Contexts and Dependency Injection 4.1 Jakarta Expression Language 6.0 Jakarta Faces 5.0 Jakarta Security 4.0 Jakarta Servlet 6.1 Jakarta WebSocket 2.2 Jakarta MVC 3.0
In addition to these, we hope that there will be an update to Jakarta Bean Validation (soon to be renamed to Jakarta Validation btw) to ensure that Validation works as expected with records.
Next week, I will be in Eastern Time for the Eclipse Foundation yearly all-hands in Ottawa. All staff will meet there to sync up and enable us to serve the Community in the best way possible. All usual activities, such as the weekly Jakarta EE Platform Call will go on as usual.
The week after, I will speak at the Amsterdam JUG since I am in Amsterdam speaking at GOTO Amsterdam that week anyway.
In last week’s Hashtag Jakarta EE, I listed all specifications planning an update for Jakarta EE 11. Among these, three of them are currently not part of the Platform. These independent component specifications, Jakarta Data 1.0, Jakarta NoSQL 1.0, and Jakarta MVC 3.0, are all candidates for inclusion in Jakarta EE 11.
Jakarta MVC standardizes the action-based model-view-controller pattern as a complement to the component-based offered by Jakarta Faces. With the bubbling conversations about moving some of the rendering back to the server in the various client-side JavaScript frameworks, Jakarta MVC may turn out to be more relevant than ever. Join the discussion to voice your opinion regarding the inclusion of Jakarta MVC in Jakarta EE 11.
From time to time, some unexpected and/or cool usages of Jakarta EE specifications pop up. This week, Richard Schilling sent an email to the Jakarta EE Platform mailing list telling about his efforts to use Jakarta EE on Android. Check out jakartaee-mobile on GitHub.
Welcome to issue number one hundred and seventy-nine of Hashtag Jakarta EE!
Planning for Jakarta EE 11 continues. There was a rush of requests for plan review submitted this week. At the moment, the specifications that are planning an update for Jakarta EE 11 are:
Those marked with (*) already have approved plans, so a plan review is not necessary for this release. Also note that Jakarta Data, Jakarta NoSQL, and Jakarta MVC are currently standalone specifications being discussed for inclusion in the Platform. Out of these three, my guess is that Jakarta Data is the one most likely to be included. There is an issue in the Jakarta EE Platform issue tracker to capture the discussion around this. Please do chime in if you have an opinion about it. Following this discussion, there will most likely be a formal vote on the Jakarta EE mailing list.
Last week’s trip to JPrime 2023 in Sofia, Bulgaria was the last of four conferences I spoke at in May. Summer is approaching, and conference season is starting to wind down. My next conference will be GOTO Amsterdam at the end of June. While I am there, I will also speak at the Amsterdam JUG. More details will follow when the details are carved out.
JPrime is a very friendly conference that is a pleasure to speak at. This year it attracted around 1250 attendees, and with two parallel tracks, all speakers get a decent crown in their presentations.
The venue is great, with an outdoor area to escape the crowds in the exhibition area and enjoy the Sofia sun in between sessions.
No conference without #runWithJakartaEE. JPrime was no exception. We had a morning run before each of the two conference days in addition to the day after the conference. The runners were Yarden, Emily, Grace, Heinz, Tagir, and me as you can see in the gallery below.
Welcome to issue number one hundred and seventy-eight of Hashtag Jakarta EE!
The due date for submitting plan reviews for specifications that are candidates for Jakarta EE 11 is May 30. And that date is fast approaching! The pull requests for those that are ready are labeled as Plan Review in the Jakarta EE Specification Committee’s GitHub repository.
A great way to get involved in specification work is to participate in the discussions happening in the GitHub issue trackers for the various specifications. An example is the discussion about HTTP status codes going on in Jakarta REST. Please chime in if you have an opinion or any relevant industry experience that can help guide the decision.
May is a busy month for conferences. Next week, I am going to Sofia to speak at JPrime 2023. It’s been a while since I was at JPrime, so I am very much looking forward to it! Check out the cool speaker promo they created for me.
Relax, I won’t bug you with the link to the course I created for LinkedIn in every Hashtag Jakarta EE, but bear with me for a while. If you are new to Jakarta EE or just want to complete a course for the Jakarta EE skill on LinkedIn, I have just published an overview course of Jakarta EE on LinkedIn Learning. Check it out, and tell me what you think!
This was my second time speaking at Infoshare in Gdańsk, Poland. The conference is pretty huge. Rumor has it they were expecting more than 6500 participants over two days, and the exhibition floor was absolutely massive!
With a focus on startups, investors, marketers, and the like, the audience on the DEV JAVA stage was, as expected, a little limited. Most of the stages, DEV JAVA included, were located in the exhibition hall. The sound system was pretty good, so it was not really a problem for the attendees to follow a talk. But as a speaker, it is very disturbing with all that background noise.
The most important track at any conference is the hallway track where you meet and network with new and old friends in the community. As depicted by Iris Classon, Reza Rahman, Adam Bien, Gerrit Grunwald, and myself here.
The hotel where most of the speakers stayed was located close to a park that is perfect for running. True to tradition, I invited everyone that wanted to join me in exchange for a Jakarta EE running T-shirt. This time Grzegorz Pinowarek joined me for a real forest trail experience in the woods.
Welcome to issue number one hundred and seventy-seven of Hashtag Jakarta EE!
It is only a little over a week until the plan reviews are due for the component specifications. You can check out the content of the reviews in the pull requests labeled Plan Review in the Jakarta EE Specification Committee Issue Tracker on GitHub.
For an overview of the ingredients that are currently being discussed for inclusion in Jakarta EE 11, check out the issues labeled EE11 in the Jakarta EE Platform Issue Tracker on GitHub. Also, make sure to check out the minutes from the weekly Jakarta EE Platform Project calls.
As I mentioned last week, I have spent this week at home. On Tuesday next week, I am headed to Gdańsk in Poland for Infoshare 2023 where I will present how to migrate from Spring Boot 2 to Spring Boot 3 focusing on how to handle the various scenarios involving the javax.* to jakarta.* namespace change made in Jakarta EE 9.
