Hashtag Jakarta EE #152

Welcome to issue number one hundred and fifty-two of Hashtag Jakarta EE!

In the previous Hashtag Jakarta EE, I mentioned the release of Spring Framework 6.0 – the first major release in five years. This week, it is time for Spring Boot 3.0. Can you imagine that Spring Boot 2.0 was released 4.5 years ago? It feels like yesterday.

As with Spring Framework 6.0, Spring Boot 3.0 raises the baseline to Java SE 17, supports Jakarta EE 9, and selected Jakarta EE 10 specifications. It also comes with support for generating native images with GraalVM.

I suspect that when developers start their migration to Spring Framework 6.0 and Spring Boot 3.0 from earlier versions, they may face challenges due to the namespace migration from javax.* to jakarta.*. I have been pointing this out in all my Jakarta EE talks over the last couple of years, but since the audiences have mostly been those migrating from earlier versions of Jakarta EE, or Java EE, many Spring developers may have missed out on this. In an effort to make this a little more palatable, I have started submitting an abstract for a talk called Jakarta EE for Spring Developers. In this talk, I will address the namespace migration challenges specifically for applications based on Spring/Spring Boot. The first opportunity to attend this talk will be DeveloperWeek in Oakland, in February next year.

It is just a little more than one week until JakartaOne Livestream 2022 on December 6. If you haven’t registered yet, please do so now so you don’t miss out on anything. This 12+ hour event is a perfect way to wind down for the holidays.

As always, we have a food-related competition where you can win great prizes and glory. This year, we are going for Jakarta EE themed snack! It can be based on fruit as shown below but doesn’t have to be. If you’re more into salty or sugary snacks, that’s fine too. Just go crazy with whatever your taste is!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.