Jakarta EE

The month of May was very busy with activities related to Release 9.1! Jakarta EE development and innovation is definitely taking off at full speed.

The hibernate-core-jakarta artifact implements the Jakarta JPA 3.0 specification, while the hibernate-core artifact still implements the Jakarta JPA 2.2 specification.

The accelerated innovation we’re seeing in Jakarta EE, and the growing number of compatible implementations, are clear signs that enterprise Java is experiencing a renaissance.

Nowadays it’s easy to get up and running WildFly standalone server in a container. But what if you need to enable clustering in Managed Domain mode which is one of the key features of Jakarta EE in general? That is not an easy task.

Welcome to the seventieth issue of Hashtag Jakarta EE!

Welcome to the sixty-eighth issue of Hashtag Jakarta EE!

The GlassFish team has been working on cleaning up the code base, and making the release compatible with newer JDK versions.

Surveys often seem to come around when we’re busiest and feel we can’t afford to take time to answer questions. However, a few minutes of your time can have important benefits down the road to everyone in the Java ecosystem.

Quarkus and Jakarta EE are gaining on Spring/Spring Boot as the most popular approach to moving Java applications to the cloud.