Posts tagged JakartaEE (12)

The Payara Monthly Catch: April 2022

Every month, we collate the very best content for our specific enterprise Java - Java EE, Jakarta EE and MicroProfile - community. We also look further afield, and where it applies, include interesting blogs, videos and articles on subjects such as DevOps, cloud computing, microservices, software architecture and more. 

TL;DR: We know our audience and if we think you will find something very useful when developing enterprise Java applications - it makes the cut! 

How Does Payara 6 Affect Your Application’s Future?

The release of Payara 6 Community in a few weeks will be a turning point for many of our users. It's important you review all possibilities in advance. Consider migration to be supported, secure and maintain peace of mind!   

We recommend moving to Payara Enterprise,  which we consider the most cost-effective and business-savvy choice. In this blog we explain 5 different scenarios.

What's New in the April 2022 Payara Platform Release?

The April 2022 Payara Platform release is here! Payara Platform Community 5.2022.2 brings 13 bug fixes, 2 component upgrades, 3 improvements and 3 security fixes, whilst Payara Platform Enterprise 5.38.0 includes 2 bug fixes, 1 improvement and 4 security fixes. 

It includes the fix for "Spring4Shell", and improved support for Jakarta EE 9, as you can now run Jakarta EE 9 applications using PrimeFaces.

This release also gives Payara users the ability to use gRPC, the Google Remote Procedure Call Framework.

Please note: This is the penultimate Payara 5 Community release. Payara 6 Community will soon take its place, to be used with Jakarta EE 10. If you want to keep using earlier Java EE/Jakarta EE versions - we encourage you to move to Payara 5 Enterprise.

Easy Jakarta EE Integration Testing with the Payara Platform and Testcontainers

One major issue when developing modern enterprise applications is the "works on my machine" problem: when an application works well on your machine but is not functional in production or even on a colleague's machine. An even more prevalent problem is to maintain the quality of ever-changing applications during development and maintenance. 

This is especially prevalent when Jakarta EE applications are developed and not properly tested in an isolated and cohesive manner. Proper integration testing helps to avoid both the "works on my machine" problem, and ensures developers can change the application effectively without breaking it. However often teams struggle with it, due to a lack of standardized testing solutions and the unpredictability of real-world conditions. 

Here, I present an effective method for Jakarta EE integration testing, using Payara Platform and Testcontainers in my example.

What is Jakarta EE?

Java is the world’s third most used programming language, and the basis of some of the world’s biggest software projects.

If you are running a large, enterprise application - supporting commercial projects - Java alone may not be enough. You need to use it with Jakarta EE, formerly called Java EE.