JBoss EAP Continuous Delivery 18 Release Notes
For Use with JBoss Enterprise Application Platform Continuous Delivery 18
Chapter 1. About JBoss EAP Continuous Delivery 18
The JBoss Enterprise Application Platform continuous delivery (JBoss EAP CD) release 18 is a Technology Preview release available in the cloud only. This JBoss EAP CD release introduces a new delivery stream of JBoss EAP, which provides incremental updates and new capabilities on a regular schedule for Red Hat OpenShift Online and the Red Hat OpenShift Container Platform.
The purpose of this new delivery model is to quickly introduce new features ahead of the traditional JBoss EAP GA release. The JBoss EAP CD releases are only available in the OpenShift image format and can be accessed from the Red Hat Container Catalog.
Traditional JBoss EAP GA releases, the next being JBoss EAP 7.3, will be based on an aggregate of JBoss EAP CD releases and will continue to be available through the normal distribution methods.
This continuous delivery release for JBoss EAP is 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.
1.1. Differences Between JBoss EAP and JBoss EAP Continuous Delivery
There are notable differences between the JBoss EAP product and the continuous delivery release for JBoss EAP.
For descriptions of differences and details about feature support in the continuous delivery release for JBoss EAP, see the comparison table in Getting Started with JBoss EAP for OpenShift Container Platform or Getting Started with JBoss EAP for OpenShift Online.
Chapter 2. New Features and Enhancements
Ability to Combine Multiple Security Realms for Authorization in an Aggregate Realm
You can now use multiple security realms for authorization in an
aggregate-realm with the
For more information, see Configure Authentication and Authorization Using Multiple Identity Stores in the How to Configure Identity Management guide for JBoss EAP.
Ability to Use the Subject Alternative Name Extension From X.509 Certificate as the Principal
You can now configure an evidence decoder to use a subject alternative name from an X.509 certificate as the principal associated with that certificate.
For more information, see Configuring Evidence Decoder for X.509 Certificate with Subject Alternative Name Extension in the How to Configure Server Security guide.
Ability to Combine Multiple Evidence Decoders with Aggregate Evidence Decoder
Elytron now provides an aggregate evidence decoder to combine two or more evidence decoders into a single decoder.
For more information, see Configuring an Aggregate Evidence Decoder in the How to Configure Server Security guide.
Certificate Revocation Capability using OCSP
Elytron now provides certificate revocation capability using Online Certificate Status Protocol (OCSP), defined in RFC6960, when undertow is used as a load balancer.
Syslog Audit Logging Enhancements
A new attribute,
reconnect-attempts, is now available to configure the maximum number of times Elytron attempts to send successive messages to a syslog server before closing the connection when using UDP.
Client and Server Interceptors
JBoss EAP 7.2 and earlier only supported EJB interceptors configured in the container.
In JBoss EAP 7.3, client interceptors and server interceptors are now supported. Client and server interceptors can be configured globally.
Ability to Specify Ranked Multiple Routes Session Affinity
You can now specify session affinity as an ordered list of nodes. If your load balancer supports multiple, ordered routes, in the event of a primary node failure, it can choose the optimal nodes in the order defined. It also ensures a definite failover target, if the primary owner of a specific session is inactive.
For information about the ranked affinity options, see The distributable-web subsystem for Distributable Web Session Configurations in the Development Guide for JBoss EAP. For information on how to enable ranked session affinity in your load balancer, see Enabling Ranked Session Affinity in Your Load Balancer in the Configuration Guide for JBoss EAP.
Enabling Statistics for Remote Cache Containers
You can now use the HotRod client to expose remote cache container statistics. The
statistics-enabled attribute can be configured for remote cache containers using the management CLI. For more information, see Configuring Remote Cache Containers in the Configuration Guide for JBoss EAP.
2.5. Web Services
Optional <T> Parameter Types Available for RESTEasy
RESTEasy now supports the following
java.util.Optional parameters as wrapper object types:
For more information, see
java.util.Optional Parameter Types in the Developing Web Services Applications book for JBoss EAP.
Reduce Memory Footprint with Galleon Feature-packs
You can now customize the main JBoss EAP for OpenShift image configuration to include only the capabilities that you require, thereby reducing the memory footprint. The provisioning tool, Galleon, offers several layers that you can select to control the capabilities present in the JBoss EAP server.
Additionally, you can package customized capabilities as Galleon feature-packs that are installed during the JBoss EAP server Galleon provisioning. For JBoss EAP for OpenShift Source-to-Image (S2I), you can build your feature-packs offline, deploy them to Maven and reference them in your
EAP Operator for Automating Application Deployment on OpenShift
JBoss EAP now offers EAP operator, a JBoss EAP-specific controller, to automate common deployment-related tasks. You can install the EAP operator using OperatorHub, the graphical interface that OpenShift cluster administrators use to discover, install, and upgrade operators.
EAP Operator for Safe Transaction Recovery and EJB Remoting
The EAP operator ensures safe transaction recovery in your application cluster by verifying that all transactions are completed before scaling down the replicas and marking the pod as
clean for termination.
The EAP operator uses
StatefulSet for the appropriate handling of EJB remoting and transaction recovery processing. The
StatefulSet ensures persistent storage and network hostname preservation even after the pods are restarted.
Calculate JVM Memory Settings
JBoss EAP 7.2 and earlier did not address conditions where JVM memory settings are higher than the container limit.
The OpenShift JBoss EAP image can now calculate default JVM memory settings when a container limit has been defined and the JVM memory settings are higher than the container limit.
2.7. Quickstarts and BOMs
New Client BOM for JAX-WS
JBoss EAP now provides a new client BOM,
wildfly-jaxws-client-bom, to manage JAX-WS dependencies. For information on how to add the
wildfly-jaxws-client-bom dependencies to your project, see JBoss EAP Client BOMs in the Development Guide for JBoss EAP.
Chapter 3. Resolved Issues
See Resolved Issues for JBoss EAP CD 18 to view the list of issues that have been resolved for this release.
Chapter 4. Fixed CVEs
JBoss EAP Continuous Delivery 18 does not include any fixed CVEs.
Chapter 5. Known Issues
See Known Issues for JBoss EAP CD 18 to view the list of known issues for this release.
Revised on 2019-12-05 13:51:34 UTC