JakartaOne Livestream is a one-day virtual conference that focuses on Cloud Native Java, MicroProfile, and Jakarta EE. The Call for Paper is open from July 15 to September 15. But don’t wait, submit your abstract NOW for a chance to speak at an event attended by more than 1000 participants. Check out the previous events for inspiration:
Eclipse GlassFish 6.1.0.RC1 passes the Jakarta EE 9.1 TCK and is available for download. The TCK project is in the process of wrapping up everything for the release. We plan to initiate the review ballot for the Jakarta EE 9.1 specifications on April 30, which means that the artifacts will be released to Maven Central on May 14th. This is a soft launch as we have been doing the last couple of releases, so the official release date with all the marketing splash around it will be May 25th.
Worth noting for this release is that it looks like GlassFish won’t be alone as a compatible implementation when the specification is ratified. A number of vendors are working hard to have their implementations available along with Glassfish for the release review ballot.
I guess it is safe to say that we were blown away by the number of detailed plans and outlines submitted as pull requests to the Jakarta EE Specifications repository. Just take a look at the list below grouped by major and minor updates to the specifications.
Major updates Jakarta Authentication 4.0 Jakarta Authorization 3.0 Jakarta Concurrency 3.0 Jakarta Expression Language 5.0 Jakarta Faces 4.0 Jakarta JSON Binding 3.0 Jakarta RESTful Web Services 4.0 Jakarta Security 3.0 Jakarta Servlet 6.0 Jakarta SOAP with Attachments 3.0 Jakarta Standard Tag Library 3.0 Jakarta XML Binding 4.0 Jakarta XML Web Services 4.0
Minor updates Jakarta Activation 2.1 Jakarta Connectors 2.1 Jakarta JSON Processing 2.1 Jakarta Mail 2.1 Jakarta MVC 2.1 Jakarta Persistence 3.1 Jakarta Server Pages 3.1 Jakarta WebSocket 2.1
I can’t wait to dive into the details of these plans as they progress through the plan reviews stipulated by the Jakarta EE Specifiation Process. Take a look at the JESP Guide for a simple walk-through of the process.
Over the past year, the Eclipse Foundation spoke to leading Java developers around the world to discuss why they rely on Jakarta EE and the unique benefits of using Jakarta EE technologies. Their input is captured in our white paper, which describes the important advantages Jakarta EE offers today and for the future.
With Jakarta EE’s long history as Java EE, it’s sometimes easy for developers to dismiss the technology as yesterday’s approach. But Jakarta EE technologies are embedded, and relied upon, in a way no other technologies are. Here are some examples you might not be aware of:
Eclipse Jetty is a certified implementation of Jakarta Servlet 5.0
Spring Boot embeds Eclipse Jetty or Apache Tomcat as a runtime
Open Specifications Bring Important Advantages
One of the advantages every one of the developers raised was the value of the specification-based approach to technologies in Jakarta EE.
The clear boundary between fully tested specifications and underlying implementations means developers can easily switch between the implementations with minimal impact on the application code. This agility saves considerable time, effort, and money when changes are required.
Jakarta EE Provides a Unique Combination of Features and Functions
The developers also described a combination of strategic and technical advantages that aren’t available in any other platform. Some of the main Jakarta EE benefits they noted include:
Stability and backward compatibility. Jakarta EE provides a mature and proven foundation for innovation that allows organizations to fully leverage the investments they’ve already made in enterprise Java applications.
Architectural flexibility. Organizations can support cloud-based microservices architectures, as well as traditional, monolithic architectures. They can also seamlessly incorporate newer technologies, such as MicroProfile, Docker containers, and Kubernetes orchestration.
Speed and simplicity. A Jakarta EE application can be set up with significantly less configuration compared to other frameworks.
Development and deployment freedom. Developers can use any Jakarta EE-compatible runtime, and they can implement and blend whichever aspects of the application server are needed to leverage Jakarta EE capabilities in a modern and efficient way.
Longevity. The open, vendor-neutral, and community-driven approach at the Eclipse Foundation ensures applications developed using Jakarta EE will remain relevant and usable over the long term.
Get the Full Story
These insights are just a few of the reasons leading Java developers remain committed to Jakarta EE. For the complete story, download the white paper.
It is time for a new edition of Studio Jakarta EE LIVE! This time I have Emily Jiang from IBM with me in the studio. We will talk about MicroProfile 4.0 and I am pretty sure that Emily will show some cool demos as well.
MicroProfile 4.0 contains updates to all the specifications. It is based on the Jakarta EE 8 versions of the four specifications that form the foundation of MicroProfile. This means that it is still on the javax.* namespace.
How difficult the migration from the javax.* to the jakarta.* namespace is for your particular use case depends on the complexity of your application. The focus has mainly been on the Java package names, but there are some other areas that may require some effort as well. Check out my Migration Guide for an example of how to migrate an application that touches most of the areas.
Please reach out to me if you discover areas that I have missed in the guide. I will be happy to update it!
There is only one more stop planned on the Jakarta EE Virtual Tour. We really enjoy giving these talks, so please reach out if you are interested in hosting us at your JUG or MeetUp.
This is the last Hashtag Jakarta EE in 2020. But don’t worry, I will continue these weekly updates in 2021 as well.
This week, MicroProfile 4.0 was released! It’s been a long wait since the previous release (3.3) back in February. But now it’s here, the first release of MicroProfile following the MicroProfile Specification Process (MPSP).
This release contains updates to all specifications. See the MicroProfile Presentation for details. Note that the four Java EE 8 specifications that form the foundation of MicroProfile have been updated to the Jakarta EE 8 counterparts. This means that MicroProfile is still on the javax.* namespace. I expect that there will be a release during 2021 that will be based on Jakarta EE 9 versions of the specifications and by that support the jakarta.* namespace.
MicroProfile 4.0 will be covered in detail in the next Studio Jakarta EE LIVE as my guest on January 28th is Emily Jiang. Make sure to tune in to get all information about the 4.0 release directly from Emily.
As I mentioned in the previous Hashtag issue, I will participate in a Tech Summary Panel organized by the Barcelona JUG on December 29. In this event, we will summarize 2020 and look ahead towards 2021. It has an amazing lineup of speakers, and I am honored to be among them. You don’t want to miss this!
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!
The election for the Java Community Process (JCP) Executive Committee (EC) has started! The ballot is open for voting until November 16, 2020. But don’t wait, submit your vote today!
Check out the nominees for the 2020 Executive Committee Election if you want to see who the candidates are. But really, the only thing you need to know is that you should vote for Eclipse Foundation. Remember that a vote for Eclipse Foundation is a vote for the Open-source Community!