It's January, and the Payara engineering bakery has been busy with the first release of the year. The Payara Platform Community 6.2023.1 release is hot out of the oven with 8 component upgrades, 1 improvement and 1 security fix. Payara Platform Enterprise 5.47.0 also comes with 14 component upgrades, 2 improvements, 3 bug fixes and 1 security fix. 

Jakarta EE has action and component based frameworks for building web applications using the model view controller architecture pattern. The much older Jakarta Faces is a component based framework while the much newer Jakarta MVC is an action based one. This blog starts by defining the two types, then takes a look at Jakarta MVC, what it is and how to get started.

Batch processing is an integral part of enterprise applications. Reading, processing and storing vast amounts of data is mostly suited to batch processing runtimes that are optimized for such workloads. Inventory processing, payroll, report generation, invoice/statement generation, data migration, data conversion among others are all tasks that are suitable to batch processing.

Batch processing typically involves breaking data loads to be processed into smaller "chunks," which are also broken down into even smaller units for processing. The batch processing is then carried out on a single unit of the data, one at a time, without any human intervention. This makes the processing of a significantly large amount of data very efficient and fast. Batch processing can also be parallelized to take advantage of the hardware capabilities of the underlying computer. 

This blog series will show you how to create batch processing tasks on the Jakarta EE Platform. The blog is broken down into a series of posts, each blog covering a specific part of the batch specification. This blog introduces you to the Jakarta Batch specification and gives a high level overview of what constitutes a batch task.

The Jakarta Contexts and Dependency Injection API is the standard dependency injection framework on the Jakarta EE Platform. The latest version of the CDI specification that shipped withJakarta EE 10 is CDI 4.0. This release features a split of the core CDI API into Lite and Full. CDI Lite is designed to run in more restricted environments, and features a subset of the original features. CDI Full contains the Lite and all other features that were in core CDI in previous Jakarta EE releases.

Therelease of Jakarta EE 10marked the dawn of a new era for the platform. This release is the first major, community driven release of the platform since it was transferred to the Eclipse Foundation. As a community driven project, the platform is open for everyone to contribute to. One of the advantages of using Jakarta EE for your projects is that you can directly have a say in the direction and future of the platform. With Jakarta EE 10 out of the way, the focus will soon shift to the next release, Jakarta EE 11.

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. 

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. 

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.