The defacto way of accessing relational data in a Jakarta EE application is through the use of the Jakarta Persistence API. For NoSQL data access, one can now use the much newerJakarta NoSQL API. Jakarta Persistence especially has worked quite well and been serving its purpose with both its support for native queries, JPQL and Criteria queries. However, modern data access paradigms have meant having to pull in third party libraries to enjoy some more abstractions. 

The Eclipse MicroProfile project is a Jakarta EE based project that augments the platform with cloud-native APIs for developing applications for the cloud. MicroProfile has had five previous version releases, with the latest being 6.0. Versions prior to 6.0 were built on the Jakarta Contexts and Dependency Injection, Jakarta RESTful Web Services and Jakarta JSON APIs. 

It's the final release of the year and the final release of Payara 5 Community!

Payara Platform Community 6.2022.2 brings 20 component upgrades, 8 bug fixes, 2 security fixes and 4 improvements. Payara Platform Enterprise 5.46.0 brings 45 component upgrades, 13 bug fixes, and 2 security fixes.

Payara Platform Community 5.2022.5 is the final release of the Payara 5 Community stream.

All releases contain a key fix for a vulnerability in web applications deployed as the default module of an instance's virtual server configuration. Read more details below!

Payara in the Press! Steve Millidge, our CEO and Founder, was interviewed by Hosting Advice about our new product, Payara Cloud.   

Introduction to Jakarta EE Frequently Asked Questions (FAQs)

Jakarta EE (formerly Java EE)  is a software development platform built on top of the Java Standard Edition, for creating modern applications of all types and sizes for the cloud or in-house. It has gone through a number of evolutions to its present Jakarta EE incarnation. The goal of this blog post is to answer commonly and frequently asked questions about Jakarta EE and enterprise Java software development in general. There are a number of old preconceived notions out there about the platform. This blog post seeks to shed light on a number of these notions within the context of the current platform. 

Welcome to our monthly roundup of the best content in the Java, Jakarta EE, DevOps, cloud computing, open source and enterprise software space!

During deployment of Jakarta EE applications to the Payara Server, all the xml files (e.g. web.xml, persinstence.xml) are verified against its schema.

Payara Platform includes all standard Jakarta EE schema, so there is typically no reason to download external schema to check against xml files. However, if the application uses external schema, in very rare cases, there may be an error during deployment. In this blog, I describe a quick fix to avoid this. 

The Representational State Transfer or RESTful architecture is a stateless, HTTP based communication standard for modern applications. It was originally proposed by Dr. Roy Fielding in hisPhD thesis. It has, over the years, become the default, programming language-agnostic means of enabling machine-to-machine communication. An application written in the Django framework in Python can have REST resources that are consumed by another application written in Java with Jakarta EE. Similarly, a Jakarta EE application can create resources that can be consumed by a C# application.  

Low on time and want to know what an 'application server' really is?

We offer our explanation. This video covers the difference between application servers and web servers, what an application server can do to make your life as a developer easier, and more, all in less time than your average pop song!

This is a high-level view that might be helpful to pass on to managers and procurement teams who aren't sure what an application server is.

JavaPro has created a training course on how to develop modern cloud-native microservices with Payara Micro and MicroProfile.

We have free tickets available, usually worth €1,690 each!