Jakarta EE40 articles

In this article, we take a look at how to get started developing RESTful web services on the Jakarta EE Platform using the Jakarta REST API.

High availability is achieved in Chronicle FIX by failover, where workload is transferred from a primary engine to a secondary engine in the event of a primary engine failure.

Learn why Jakarta Faces is a great choice especially as a Java developer when you need a UI framework for your application!

The latest version of Jakarta REST is 3.1, which shipped with Jakarta EE 10. This version comes with two great new noteworthy features!

Want to have a say in what happens for the next version of Jakarta EE? Check out the new edition of the Jakarta EE Survey 2022 by OmniFish!

Learn the difference between application servers and web servers, what an application server can do to make your life as a developer easier!

Payara has launched a new product Payara Cloud, designed to run Jakarta EE apps easily and quickly on the cloud.

Since there’s so much existing code using Enterprise Beans (EJB), a certain level of support is still desired. Piranha Cloud takes a somewhat novel approach to Enterprise Beans and maps Enterprise Beans annotations to equivalent functionality in CDI or other Jakarta EE APIs.

EJB, or Enterprise Beans, are Java classes with a number of container provided services attached to them, such as transactions, remoting and security. A possible future direction for EJB is to rebase it on CDI. Instead of having those two essentially competing component models in Jakarta EE, we would end up with just one.

gRPC is an open source Remote Procedure Call framework; an alternative to REST. Find out more and how Payara is involved!