Upcoming Java 21 brings a bunch of new features, including very interesting progress in concurrency. There are two main improvements – virtual threads and structured concurrency.

In this article, we discuss incoming usage of these enhancements inJakarta EE (formerly Java EE, now an open source project maintained by the Eclipse Foundation), a set of specifications that enables the worldwide community of Java developers to work on cloud native Java enterprise applications. Jakarta Concurrency is the concrete specification describing the expected behaviour.

The support in Jakarta EE is currently under development, details may change in the final implementation.

Apache NetBeans is a popular IDE for Java development, offering a wide range of features for streamlining the development process. Payara Server, a robust and scalable option for deploying Jakarta EE applications, seamlessly integrates with Apache NetBeans. In this blog, we explore the seamless usage of Payara Platform 6 within Apache NetBeans, highlighting the benefits and demonstrating how it enhances your development workflow. Whether you're starting a new project or working with an existing app, this guide helps you leverage the power of Payara Server in your development process. Follow the steps in this blog to set up Apache NetBeans to use Payara Server for running your web apps.

Why is software testing so important? Firstly, because we are all susceptible to making mistakes.
Secondly, because the sooner we find bugs and fix them, the cheaper the fix!

Jakarta EE is at the forefront of innovation in enterprise Java. This means staying close to the community and working on new specifications to meet developer needs.

In my previous blog post,here,I examined the JSR-375 specifications and their implementation by Jakarta EE and, more specifically, by the Payara Platform (Server and Micro).

I presented a brief overview of the JSR-375 specifications and their new features, focusing on the notion of Identity Store and illustrating, with a simple example, one of the most common use cases: the LDAP (Lightweight Directory Access Protocol) based authentication and authorization process.

Our CEO and FounderSteve Millidge is a guest on the WaterWorks podcast, the technology discussion podcast run by journalist and authorJohn K. Waters. 

Waters is the editor in chief of theConverge360 news and information sites Application Development Trends(ADT Mag), Pure AI, and Futuretech360 - with his career also including writing books, including "The Everything Guide to Social Media," one of the first deep dives into this world-changing phenomenon, and "Blobitecture," an exploration of an architectural and industrial design trend enabled by computer software. He also co-scripted the documentary film "Silicon Valley: A 100 Year Renaissance," which aired on PBS.

Steve had a conversation over Zoom with John. Steve - in Malvern, England, after work - spoke to John - in his Silicon Valley office just before 9am. Their discussion was wide-ranging and insightful, covering everything from the future of Jakarta EE and how it will fare under Eclipse Foundation stewardship, to the specifics of Payara's journey and how we got our marine logo! It's a must listen for those interested in open source and Enterprise Java. 

Introduction

When performing the configuration of the Payara Server for your application, you often need to supply a password. The password to connect to the database is a classic example, but there are many situations where you need to enter this kind of sensitive data.

With Payara Server, you have the option to hide this kind of sensitive data from the user, so that this information is much better secured.

There are a lot of monitoring and alert mechanisms available within Payara Server. For example, it is possible to report user requests or database calls that take too long, or to report when high CPU or high memory usage occurs. But it is sometimes not easy to identify 'why' a request takes such a long time.