GlassFish 7.0.0-M7 passes the Jakarta EE 10 Platform TCK. The issues that are left affect the TCKs for Jakarta EE 10 Web- and Core Profiles. There is light at the end of the tunnel, but it is hard to predict precisely when these issues will be resolved. The best way to stay informed is to join the platform call on Tuesdays and/or follow the mailing lists, and of course follow the Hasthag Jakarta EE blog series.
The proposal for the Jakarta Data specification has completed the community review, and it is now being prepared for creation review ballot by the Jakarta EE Specification Committee. All according to the Jakarta EE Specification Process (JESP).
And, if you are into running, I will arrange a Jakarta EE Community Morning run at least one of the days of the conference. Look out for #runWithJakartaEE on social media when we’re closer to the event.
Next up for me, if the traveling gods are still with me, is JBCNConf in Barcelona from July 18 to 20. I will present a talk titled Jakarta EE 10 – Feature by Feature, and Tanja will present Jakarta EE: Community Power and Progress.
Here’s some good news if you are a sucker for cool swag. While I was at the Eclipse Foundation All Hands meeting this week, I picked up a bunch of swag to give away at the upcoming conferences. When I checked in to my flight at Ottawa Airport, I discovered that mouse pads are heavier than they look. Solved it by taking them as hand luggage. Part of the story is that my baggage is loaded with maple syrup, so it was already quite heavy 😋
The program for EclipseCon 2022 has been published! The conference will be in Ludwigsburg, Germany from October 24 to October 27 later this year.
There is no fast track for Eclipse Foundation staff to speaking slots at EclipseCon. We have to submit abstracts just like anyone else aspiring to become an EclipseCon speaker. Luckily, I got two talks accepted. One of which I am listed as co-speaker.
The Eclipse GlassFish project is working on a fix for 1), and there are Pull Requests being discussed for 2) and 3), so there is a small possibility that the Jakarta EE Platform, Web– and Core Profile can be ready for release review ballots the upcoming week.
I had a great trip to DWX’22 last week, even if the travel home took a little longer than planned. A flight turned into a train ride and an extra night at a Frankfurt Airport hotel before an early morning flight back home. Now, let’s see how Tomorrow’s trip to Ottawa will be affected by striking pilots…
Jakarta EE 10 isn’t quite released yet, but that doesn’t stop us from celebrating the release. Check out the recording of the Jakarta EE 10 Release Celebration if you weren’t able to join us live last Tuesday.
The release itself is imminent. There are a couple of TCK challenges that need to be sorted out and dealt with to get everything to pass. GlassFish 7 currently passes the Jakarta EE 10 Platform TCK, but there are some changes required in the Jakarta Concurrency 3.0 TCK related to Jakarta Concurrency now being a part of Jakarta EE 10 Web Profile. It was not required for the Web Profile in previous releases, and some cleanup with regards to the packaging of the test deployments has to be cleaned up. Jakarta EE 10 Core Profile has some similar issues, but this is regarding some of the tests for Jakarta RESTful Web Services 3.1 still references Jakarta XML Binding 4.0. This works well for Web Profile, where Jakarta XML Binding is required, but not for Jakarta EE Core Profile where it’s not.
So to sum up, it is very close. Just some small nits that have to be dealt with. Then we should be ready to go!
I will most likely go for a run in one of the parks in Nürnberg on Thursday morning. Let me know if you’re into running and want to join me. If I know you’re coming, there is a cool Jakarta EE functional T-shirt in it for you. Werner, I’ve got you covered 🙂
This week, I was back in Kraków for Devoxx Poland. I have been to most Devoxx conferences before, but this was my first visit to Devoxx Poland. It is a great conference at the modern Kraków Congress Center close to the city’s center. I’ll provide a write-up of this conference in the coming days.
So, Jakarta EE 10? Are we there yet? Due to travel and Midsummer this week, I’m not 100% up-to-date on the status, but the last I saw, the Jakarta EE Platform, Web- and Core Profile are very close to being ready for release reviews. Hopefully, we can get them moving in the upcoming week.
So, with all these celebrations and events around Jakarta EE 10, when can we expect the release? As I mentioned in Hashtag Jakarta EE #128 last week, one of the challenges is the requirement that the compatible implementation used to ratify the specification must pass all features, including the OPTIONAL ones.
To address this issue, the Jakarta EE Platform team decided to remove Entity Beans, both Container and Bean Managed Persistence (Jakarta Enterprise Beans 4.0, Optional Features, Chapters 3 – 7) OPTIONAL requirements for Entity Beans from the Jakarta EE 10 Platform specification. This will open up the possibility for other open-source implementations than Eclipse GlassFish to be used for ratifying the specification.
That said, Eclipse GlassFish is getting closer and closer to passing the TCK, so it is likely that it will pass the finishing line first anyway. From what I can see, the remaining task is to integrate an implementation of Jakarta Concurrency 3.0 and pass the new standalone TCK for this specification.
The ballot for Jakarta Security 3.0 will conclude tomorrow. This means that all of the individual specifications that are a part of Jakarta EE 10 are approved! So when can we expect Jakarta EE 10 (Platform, Web Profile, and Core Profile) to be final? The plan was to start the ballot for these specifications by June 9 and release them on June 23 with a big announcement on June 28.
That ship has unfortunately sailed due to the work with getting Eclipse GlassFish to pass all the tests in the TCK taking a little longer than expected. The reason why GlassFish is so important is that it is the only implementation that implements absolutely all features of the specifications, including the OPTIONAL ones. As the process is defined, there has to be at least one implementation that does this in order to ratify the specification. Until we either get rid of the OPTIONAL features or remove the requirement that one implementation has to implement them all, GlassFish is, and will be, the de-facto reference implementation*).
The plan is still to release Jakarta EE 10 as soon as possible. Hopefully, just a week’s delay from what was originally announced. Worst case, it slips a couple of days into July. There will still be a Jakarta EE 10 Release Celebration Tech Talk on June 28. Please sign up and join us there!
*) Note that there is no mention of a reference implementation in the Jakarta EE Specification Process (JESP). The exact phrasing is “A Specification Version must identify at least one Compatible Implementation under an Open Source License that implements all optional elements of the Specification and fulfills the requirements of all elements (including optional elements) of the TCK.“
Conference season goes on, and next week, I am going to Coimbra in Portugal for JNation. Jakarta EE will be present, co-located with the Payara booth. Come by and pick up your favorite Jakarta EE swag. I am pretty sure there will be some nice t-shirts there. And, of course, there will be a talk as well. This time, I will share the stage with Tanja. The topic of the talk is Jakarta EE 10 and Beyond.
I must admit that I haven’t really explored the Twitter Communities feature, so I don’t really know how relevant they are. Nevertheless, I created a Twitter Community for Jakarta EE last week. Please do join, participate, share, and help make it the greatest Twitter Community in the Galaxy!
Yesterday, I had the pleasure of presenting Jakarta EE at JavaDay Istanbul 2022. I have made a habit of writing a small report from the conferences I speak at. And I will do that for this conference as well, but since I am at the airport on my way home writing this week’s Hashtag Jakarta EE, I will publish the write-up from the conference early next week. Stay tuned!
The CFP for EclipseCon 2022 is open until June 15, but you still have a chance of being picked as an early bird submission if you submit it before June 1.
After a week without traveling, I will be going to Turkey the upcoming weekend for Java Day Istanbul 2022. I have spoken at an online version of this conference before, but this is the first time in person. I am looking forward to connecting with the Turkish Java developer community!
In my talk titled Jakarta EE 10 – Feature by Feature, I will go over as many of the features coming in Jakarta EE 10 as possible.
Talking about Jakarta EE 10, with one exception, all the specifications targeting this release have now completed their release reviews. The exception is Jakarta Security 3.0 since a missing piece of documentation was discovered during the review. This issue has now been addressed and the ballot will be restarted shortly. We are still on schedule, and there is room in the plan for a respin of the ballot. Ensuring quality is one of the reasons for these reviews, so it just shows that the process is working as intended.
The pull request for Jakarta EE Core Profile 10 has been created, so you can have a sneak peek of the specification documents. Please do have a look and provide feedback so we can brush off any inconsistencies, misspellings, or missing items before we start the ballot. The intention is to start this ballot at the latest on June 9, 2022.
One of the objectives of Jakarta EE 10 is to make sure that applications run as expected on both Java SE 11 and 17. That means that the Platform TCK must be passed by compatible implementations on both Java SE 11 and 17.
Currently, Eclipse GlassFish is getting closer to passing the TCK on Java SE 11, and there is still some work remaining for Java SE 17. The Jakarta EE Platform team discussed this in the weekly call last week and decided to push the release date out a month. The new target date for the Jakarta EE Platform specification to enter its release review is June 9, 2022. This means that we will still be able to deliver Jakarta EE 10 as promised in Q2, 2022.