はじめに

Jakarta EE 9のリリースは、Java Enterpriseの伝統を破るものとなります。OracleからEclipse FoundationへのJava EEコード寄贈の法的な要件は、javax名前空間をjakarta名前空間に変更することです。

しかし、Jakarta EE 9でのパッケージとXMLの名前空間の変更はまだ始まりに過ぎません。名前空間の変更により、新たな開発や機能追加が可能となりましたが、Java Enterprise仕様の一部を使用しているフレームワークやライブラリもすべて新バージョンに合わせて調整する必要があります。

Introduction

The release of Jakarta EE 9 breaks a tradition of Java Enterprise. A legal requirement of the Java EE code donation from Oracle to the Eclipse Foundation is the change of the namespace of javax to jakarta.

But the change of the package and XML namespace in Jakarta EE 9 is only the beginning. The change of the namespace allows for new development and functionality, but all frameworks and libraries using one of the Java Enterprise specifications also need to be adjusted to the new version.

In December, the biggest news was Jakarta EE 9’s official release, completing the move to the jakarta namespace. This officially took place at the Eclipse Foundation Jakarta One Livestream, where our CEO Steve Millidge took part in the keynote speech (watch here) and presented as lead on the GlassFish project (video here). 

In other major release news, MicroProfile 4.0 was made available towards the end of the month, with the delayed release set to bring in new features including alignment with Jakarta EE 8. 

Payara has also enjoyed kick-starting healthy debate this month, with our CEO Steve Millidge proposing that Ahead of Time Compilation with GraalVM isn’t always all it’s cracked up to - and watching the comments roll in!  

We are hoping to continue to make bold statements and drive forward discussion in the Java and Jakarta EE community in 2021. 

If this sparks your interest, make sure you are following us on Twitter!

The Payara Enterprise Release 5.22.0 in October 2020 was the first Payara Enterprise release to include our fully integrated and greatly improved real-time monitoring and alerting solution called Payara InSight (formerly known as Payara Monitoring Console in Payara Community).

Then in the November 2020,release, we made improvements in how alerts are represented in the user interface, the display of widget content, and configuration options.

For December’s Payara Enterprise 5.21.1 (patch release), we’ve continued to make improvements that make Payara InSight easier to use. Updates include slight changes to the GUI for consistency and warning awareness, improvements in the flow of creating new pages, and improvements to the process of updating or changing a previously created Watch.

When we develop software we don't expect to be hacked or compromised. We build great new software for the needs of our clients. The people that use our software expect that our systems are safe and data will not be compromised. To ensure that safety we need to take responsibility and develop our applications in such a way that we can meet these expectations. Since the situation is real that our application is hacked or compromised. In the guide below, we discuss 7 pointers that can help you develop applications with a minimal security risk.

There is a lot of interest in the server-side Java community around using ahead of time (AOT) native compilation provided by Graal Substrate VM to drive down memory usage and cold start times of Java microservices. While these frameworks are technically interesting, the claim is if you spend time rewriting your Jakarta EE applications to utilise these new frameworks, then you will substantially reduce your cloud operational costs. First, by enabling the adoption of a serverless deployment model and second by reducing your containers' memory usage. 

As MicroProfile moves toward the 4.0 final release, the Payara team has simultaneously been working to ready the Payara Platform for MicroProfile 4.0 compatibility. One of the goals of the Payara Platform Community Edition is to evolve rapidly and provide a place for developers to test new features and capabilities as soon as they are available. In the Payara Platform Community 5.2020.7 Release, you can give two of the MicroProfile specification release candidates a try: MP Health 3.0 and MP JWT Auth 1.2.

The last Payara Platform release of 2020 is here!  With this patch release of Payara Platform Enterprise 5.23.1, we're introducing more improvements and component upgrades to Payara InSight as well as a couple useful bug fixes. Meanwhile, the Payara Platform Community 5.2020.7 introduces some improvements and additions to the MicroProfile specs in preparation for the upcoming MicroProfile 4.0 release. We are also happy to confirm that Payara Platform Web Profile is now Jakarta EE 8 compatible!

You can download Payara Platform Community 5.2020.7 here and request Payara Platform Enterprise 5.23.1 here. 

Read more below to find out the details.

As leading contributors to the Jakarta EE project, Payara excitedly welcomes Jakarta EE 9 - now officially released! 

Announced at today’s Jakarta One Livestream, the headline breaking change is the move from the package namespace javax to jakarta across the Jakarta EE 9 Platform, Web Profile specifications, and related TCKS. 

Through our involvement in the Eclipse Foundation Jakarta EE Working Group, we are proud to play a major role in shaping, improving and championing Jakarta EE 9. The specifications will be key to the evolution of cloud native technologies for Java, also central to Payara's mission. 

Payara Server Web Profile (Enterprise Edition 5.23.0 and Community Edition 5.2020.6), has passed the approximately 18,000 open sourced licensed Jakarta EE 8 TCKs for the Web Profile Platform and is now a Jakarta EE 8 Web Profile compatible implementation. Payara Server is available for download here.