What’s New in the February 2022 Payara Platform Release?

Jakarta EE

The February 2022 Payara Platform release is here!  Payara Platform Community 5.2022.1 includes 3 improvements and 10 bug fixes. Payara Platform Enterprise 5.36 brings 3 improvements and 4 bug fixes. 

We also released a second alpha version of Payara 6, with the headline news being that it now includes support for MicroProfile 5.0!

Read more below to learn about the highlights.

You can request Payara Platform Enterprise 5.36 here.

You can download Payara Platform Community 5.2022.1 or try Payara 6 here.

MicroProfile 5.0 Support Added to Payara 6! 

MicroProfile 5.0 saw dependencies updated from javax to the new jakarta namespace. This means that MicroProfile APIs can now be used with Jakarta EE 9.1.

With the implementation of MicroProfile 5.0 in Payara 6, Payara users will be able to run their MicroProfile applications in combination with the new namespace.

MicroProfile 5.0 is the very latest release of the specifications by the Eclipse Foundation, so users can soon be confident they are at the cutting edge of microservices optimization for Enterprise Java!  

This marks the completion of the first step of our Payara 2022 roadmap, to be followed by incorporation of Jakarta EE 10 specifications ready for Payara 6 Beta, in Q2. Read more here

Community Contribution: Improvements to Deployment Speed Related to CDI Scanning 

To go back to our changes accessible in our current Payara 5 Community edition: we have found another way to speed up deployment in certain instances. 

When an application is deployed, the archive is scanned for specific CDI annotations. GitHub userLukáš Kvíderanoticed that this process was very slow for his specific application – with a timeout after 600 seconds, whilst still deploying.

His enhancement streamlined the logic, by making it so that, whenever possible, the scanning is stopped when the relevant information is gathered. This removes the need to scan the entire archive. 

This faster scanning process is very noticeable for large applications, with successful deployment achieved now after only a few seconds. Thank you Lukáš for your valuable contribution, now in Payara Community. It will undergo further testing before it is deemed secure enough for inclusion in Payara Enterprise

Automatically Fix TrustStore Corruption in ‘.gfclient’ Directory 

A TrustStore in Java holds on to certificates to identify servers, like the Admin Console running on a remote installation. Your application will use it to “trust” the third party it is communicating with, for example, an external server.

The Payara TrustStore for the Asadmin CLI tool could on rare occasions get corrupted, making remote access with secure administration no longer possible through the CLI tool. We have now improved the Client code so the file is automatically repaired, avoiding interruption of the Payara Server administration. This improvement applies to both Payara Community and Enterprise. 

You Must Soon Move to Payara Enterprise If Using Java 8

Payara Community is intended for innovation and development. As a result, it prioritises support for only the very latest versions ofJava

The source code for Payara 6 now uses JDK 11, which means Payara 6 alpha2 can only be run on JDK 11 or JDK 17.

When Payara 6 Community final is released – and becomes the current Community release – it will no longer run with JDK 8. 

Therefore, if you want to keep running your applications safely and securely with JDK 8 in the long term, we’d recommend you move to our product with a 10-year software lifecycle, Payara Enterprise. Payara 4, usable with JDK 8, is still maintained in Payara Enterprise, and will be maintained until February 2025. This means there will still be updates, bug fixes, and platform certifications for the latest infrastructure, database drivers etc.

In short, with Payara Enterprise, you will still be able to access updates and fixes for a runtime that works with your JDK 8 applications, alongside extra features. For example, in this month’s release, Payara Enterprise accesses the ability to run an embedded EJB container via a testing framework in both JDK 8 and JDK 11. You must have Payara Enterprise to access this improvement.

Release Notes 

The February 2022 Payara Enterprise Release (request here) includes 3 improvements and 4 bug fixes, whilst the Community release (direct download here ) offers 3 improvements and 10 bug fixes.

See a more detailed overview of the fixes and improvements in the Release Notes:

 

Comments (0)

Post a comment

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

Payara needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Legal & Privacy Policy.

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

Related Posts

Green stylised leaf symbol representing the Spring Framework, shown with a smooth curved shape and a small stem inside a circular or rounded background , with 'spring' written on its right side. 2 minutes
Jakarta EE

Spring Framework 7.0 and Spring Data 2025.1.0 Embrace Jakarta EE 11 Compatibility

The recent releases of Spring Framework 7.0 and Spring Data 2025.1.0 mark an important milestone for the Java ecosystem, […]

Docker logo 4 minutes
Community

Level Up Your Jakarta EE Apps with Payara 7 and New Docker Images

We’re excited to share major updates around the Docker image story for the Payara Platform Community, aligned with our […]

Timeline showing Payara Platform Enterprise 4, 5, and 6 support phases (Full, Extended, Lifetime) from 2023–2033, along with JDK 8, 11, 17, and 21 support periods and end-of-life markers. 4 minutes
Thought Leadership

Understanding the Payara Platform Enterprise Software Lifecycle: How We Support Long-Term Stability 

Keeping an application server running smoothly isn’t so much about new features, but more about predictability and consistency. Software […]