Chapter 3. Technology Preview

Important

The following configurations and features are provided as Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

See Technology Preview Features Support Scope on the Red Hat Customer Portal for information about the support scope for Technology Preview features.

New Agroal Datasources Subsystem

JBoss EAP 7.2 introduces the datasources-agroal subsystem, which is a lightweight datasource connection pool implementation that performs exceptionally well in situations with high contention on the pool. This can be used as an alternative to the current JCA-based datasources subsystem.

This subsystem is not enabled in the default JBoss EAP configuration. For information on enabling and using Agroal datasources, see Datasource Management With Agroal in the Configuration Guide.

MicroProfile REST Client

JBoss EAP now supports the MicroProfile REST client that builds on JAX-RS 2.0 client APIs to provide a type-safe approach to invoke RESTful services over HTTP. With the MicroProfile REST client, you can write client applications with executable code. The MicroProfile TypeSafe REST clients, which are defined as Java interfaces, enable programmatic and declarative registration of providers.

For more information about the MicroProfile REST client, see the MicroProfile Rest Client section in Developing Web Services Applications for JBoss EAP.

Extending RESTEasy Support for Asynchronous Request Processing and Reactive Return Types

JBoss EAP now extends the RESTEasy support for asynchronous request processing and reactive return types. This includes support for pluggable reactive types, and extensions for additional reactive classes. A new type of invoker named RxInvoker, and a default implementation of this type named CompletionStageRxInvoker are also supported. JBoss EAP also provides the ability to convert a filter into an asynchronous filter. Proxies, the RESTEasy extension that supports an intuitive programming, is extended to include both CompletionStage and the RxJava2 types Single, Observable, and Flowable.

For more information, see the Extending RESTEasy Support for Asynchronous Request Processing and Reactive Return Types section in Developing Web Services Applications for JBoss EAP.

Eclipse MicroProfile Config

JBoss EAP 7.2 implements the SmallRye Config component, which provides support for Eclipse MicroProfile Config using the microprofile-config-smallrye subsystem. This allows applications and microservices to be configured to run in multiple environments without a need for modification or repackaging.

For more information, see Using Eclipse MicroProfile Config to Manage Configuration in the Configuration Guide.

Eclipse MicroProfile OpenTracing

JBoss EAP 7.2 implements the SmallRye OpenTracing component, which provides support for the Eclipse MicroProfile OpenTracing specification. This allows requests to be traced as they go through applications and services deployed to the JBoss EAP server, and extends observability of the request’s lifecycle.

For more information about the microprofile-opentracing-smallrye subsystem, see Tracing Requests with the MicroProfile OpenTracing SmallRye Subsystem in the Configuration Guide. For information about how to customize tracing for CDI beans and JAX-RS endpoints, see Using Eclipse MicroProfile OpenTracing to Trace Requests in the Development Guide.

Eclipse MicroProfile Health

JBoss EAP 7.2 includes the SmallRye Health component, which provides Eclipse MicroProfile Health functionality. This feature allows you to check on the health of a remote node and determine if the JBoss EAP instance is responding as expected. The microprofile-health-smallrye subsystem is included in the default JBoss EAP 7.2 configuration.

For more information about the microprofile-health-smallrye subsystem, see Monitor Server Health Using the MicroProfile Health Check in the Configuration Guide. See Implement a Custom Health Check in the Development Guide for information about how to implement a custom health check.