Welcome to issue number one hundred and twelve of Hashtag Jakarta EE!

The work with Jakarta EE 10 is chugging along as February 28, the target date for release reviews is approaching. No new specifications started their release review this week, so the status is the same as it were in Hashtag Jakarta EE #111. More release reviews are expected to start in the upcoming week.

I was supposed to travel to Novosibirsk for my SnowOne on February 25-26. But due to the circumstances around the pandemic, the conference will be online-only in February. My talk will be on Saturday, February 26. Check the SnowOne website for details. There will be an in-person event in April, but unfortunately, I am not able to go there due to a conflict with another travel.

There are quite a few conferences coming up this spring and early summer. Check out the I’m Speaking sidebar of https://www.agilejava.eu/ for a quick overview. I also try to keep the list on my Speaker Bio page up-to-date as well.

The Jakarta MVC project plans to release an update to the specification around the time of Jakarta EE 10. As you are aware, Jakarta MVC is not yet a part of the Jakarta EE Platform or Jakarta EE Web Profile. With the ongoing revival of server-side rendering, we hope that some time in the future to be included in the Web Profile.

Check out Tanja’s latest blog post for a Jakarta EE 2021 Review and Community Update January 2020.

Welcome to issue number one hundred and eleven of Hashtag Jakarta EE!

A couple of release reviews for specifications targeting Jakarta EE 10 were completed this week. Jakarta Activation 2.1, Jakarta Annotations 2.1, and Jakarta Mail 2.1 are done. A couple of the pull requests for other specifications are almost done, so we can expect more reviews to start the upcoming week.

In preparation for JavaLand 2022, speakers are sharing their thoughts for the conference in Top Speaker Interviews. Check out the interviews of Heather VanCura, Ed Burns, Josh Long, and yours truly.

Remember to subscribe to the Jakarta EE Platform project’s mailing list to stay up-to-date on everything that is going on!

Welcome to issue number one hundred and ten of Hashtag Jakarta EE!

The next important date to mark your calendar within the context of Jakarta EE 10 is February 28, 2022.

This is the deadline for all Jakarta specification projects to initiate their release review in order to be a part of Jakarta EE 10. The release reviews are initiated and tracked by pull requests to https://github.com/jakartaee/specifications.  The release review of Jakarta Activation 2.1 is done. Reviews of Jakarta Annotations 2.1 and Jakarta Mail 2.1 will complete this week.

The release reviews are required by the Jakarta EE Specification Process (JESP). Take a look at the simplified JESP Guide for a quick overview.

While waiting for Jakarta EE 10, check out the new eBook titled How Jakarta EE Delivers on the Vision for Open Source Cloud Native Java. This free eBook gives you everything you need to know about Jakarta EE.

Welcome to issue number one hundred and nine of Hashtag Jakarta EE!

More and more specifications targeting Jakarta EE 10 are getting ready for their release reviews. Jakarta Activation 2.1 is done. Jakarta Annotations 2.1 and Jakarta Mail 2.1 are ongoing. More are likely to start this week. Check out the list of pull requests for the full overview.

As always, stay connected with the progress by joining the mailing lists and the public calls. Especially the weekly Jakarta EE Platform call. Details published on the Jakarta EE Specifications Public Calendar. If you’re for some reason not able to, check out the meeting minutes.

Eclipse Foundation turned 18 this week! Reply to the tweet and tell what an 18-year old is old enough to do in your country!

If the #EclipseFdn was a person, it would be old enough to vote! Join us in celebrating 18 great years, and tell us what we'd be old enough to do in your country! #CommunityIsKey #opensource pic.twitter.com/v2xQlBjvDB

— Eclipse Foundation (@EclipseFdn) January 28, 2022

Welcome to issue number one hundred and eight of Hashtag Jakarta EE!

The release reviews for the various specifications targeting Jakarta EE 10 are adding up. You can follow the progress of the reviews by looking at the Pull Requests with the materials and/or by following the ballot threads on the Public Jakarta EE Specification Committee mailing list.

There have been some discussions going on the various mailing lists regarding how to stage and release milestones and release candidates of the specification artifacts. To help with this, the Jakarta EE Platform project has written up guidelines for Milestones and Release Candidates on the Jakarta EE Platform Project Wiki.

The specification project for Jakarta RPC that I mentioned in #107 has been approved and is being set up as we speak. Join the Jakarta RPC mailing list if you are interested in participating in the project, or just want to know firsthand what’s being discussed.

Another discussion that came up on the mailing list is regarding JCache (JSR 107) and whether that could be a candidate for a Jakarta specification. Follow the email thread on the Jakarta EE Community mailing list.

If you want to learn more about what’s coming in Jakarta EE 10, do join my talk Get Ready for Jakarta EE 10! on Monday at 11:00 EST. It is streamed live on YouTube. The talk is as part of the jChampionsConference, a conference where all the speakers are Java Champions.

Welcome to issue number one hundred and seven of Hashtag Jakarta EE!

My first conference of 2022 is a wrap! Read all about it in my write-up of CodeMash 2022. In-person conferences are possible in these pre-post-pandemic times as long as care is taken and local regulations are followed. The next in-person conference I am speaking at is SnowOne in Novosibirsk, Russia. There are some moving parts to be sorted out first with regard to visas, covid-regulations, and other disruptions that may or may not happen, but hopefully, I will know more in the coming days.

Before that, I will speak at the upcoming virtual jChampions Conference. This is a conference where all the speakers are Java Champions, and it is totally free! Imagine that!

So, what is going on with Jakarta EE 10? The minutes from the weekly platform call are always a good place to look for information. Another place is the Jakarta EE Platform project mailing list which is pretty active these days. There are still two weeks until the ballot for Jakarta Activation 2.1 closes. The usual ballot period for release reviews is 14 days, but for this one, it was extended to four weeks to compensate for the holiday period.

A new specification (Jakarta RPC) has been proposed and the creation review ballot is ongoing for approval by the Jakarta EE Specification Committee. The main goal of Jakarta RPC is to make gRPC easier to use within the Jakarta EE ecosystem. It is exciting to see new specifications like this one being proposed. It shows that the goal of establishing Jakarta EE as a platform for innovation is succeeding.

Welcome to issue number one hundred and six of Hashtag Jakarta EE!

The blog entries from the jakartablogs.ee blog aggregator are now also displayed on the new blog section on jakarta.ee. Just navigate to https://jakarta.ee/blogs, or click on the Blog menu item on the top menubar.

The Jakarta EE Platform team started 2022 with the weekly calls on January 4. These calls happen every Tuesday at 11:00 ET and are open for anyone interested to join. Check the Jakarta EE Specifications public calendar for details. These calls are an excellent opportunity to discuss matters directly with everyone involved. Don’t underestimate the power of direct, synchronous communication! Especially in these times where we are stuck behind our webcams, with email threads and slack channels flowing over and important information tending to get lost in the ever-increasing amount of spam hitting us every day. If you miss a call or are interested in seeing what is being discussed, check out the meeting minutes.

The first milestone of Spring 6.0 was released this week. Check out Juergen Hoeller’s announcement. For those of you waiting for Spring Boot 3.0, the good news is that there is a milestone planned to be released later in January. Spring 6 and Spring Boot 3 are the first versions of Spring supporting the jakarta.* namespace.

Welcome to issue number one hundred and five of Hashtag Jakarta EE!

Happy New Year!

2021 is soooo last year as we now are entering 2022. This year is an important year for the Jakarta EE Community. First and foremost, 2022 is the year of Jakarta EE 10! It looks like the final release will slip a little into Q2, but the work with getting the first specifications over the finishing line is progressing. Just before New Year, Jakarta Activation 2.1 was put forward for ballot by the Jakarta EE Specification Committee. More specifications will follow now that we start returning to our desks and webcams again after a well-deserved holiday.

On the funny side, I came over the Weekend Reading List blog series by Rodrigo Graciano, JUG leader of the NYJavaSIG. He reached Weekend Reading List #104 by the end of 2021, the same as I did with my Hashtag Jakarta EE #104. That means that we must have come up with the idea to start a weekly blog series at about the same time. Keep up the good work, Rodrigo! I hope to be able to visit NYJavaSIG soon.

Welcome to issue number one hundred and four of Hashtag Jakarta EE!

Welcome to issue number one hundred and three of Hashtag Jakarta EE!

All sessions from JakartaOne Livestream 2021 are now available on the Jakarta EE YouTube Channel.

We thank everyone involved in making JakartaOne Livestream 2021 a success!

The Jakarta EE Platform team will now take a well-earned break over the holidays. The next weekly Platform call will be on January 4, 2022. Make sure to att the Jakarta EE Specifications Calendar to your calendar. The minutes from all these calls are always published on the Jakarta EE Platform Team project pages.

Logging Ad Nauseum

I guess I have to mention logging in one way or the other this week. A lot of good stuff has been written and communicated about this. All I want to say is that you should follow the advice to always use the latest recommended versions of your dependencies. Another piece of advice I will throw in is that you should always consider whether you actually need that particular dependency you just added. Take logging, for example. I have always been happy with Java Util Logging (JUL). It is provided for me by the platform, and provides the functionality I have needed.

package dukes;

import java.util.logging.Logger;

class DukeLogs {

    public static final Logger LOGGER = Logger.getLogger("dukes");

    void doStuff() {
        LOGGER.info(() -> "Duke says hello");
    }

}

This may not be the case for everyone. Log4j provides a lot of useful stuff that you may benefit from in your particular use case. But if you choose to rely on third-party dependencies, always make sure that you follow the recommendations to which version to use (usually the latest)!

See Eclipse and log4j2 vulnerability (CVE-2021-44228) to see the status of the various projects at Eclipse Foundation. Please help keep this list up-to-date for the projects you are involved in!