WildFly 28 Beta1 is released!
I’m pleased to announce that the new WildFly and WildFly Preview 28.0.0.Beta1 releases are available for download at https://wildfly.org/downloads.
New and Notable
The biggest changes in WildFly 28 Beta1 relate to the observability space.
micrometersubsystem has been added to standard WildFly, bringing Micrometer support. As part of this work, we’ve added support for Micrometer integration with our MicroProfile Fault Tolerance implementation. The
micrometersubsystem was first introduced in WildFly Preview in WildFly 27. Note that the subsystem has been updated from what was in WildFly Preview 27 to switch to pushing metric data via OTLP to a remote collector, instead of supporting polling of data on the WildFly server’s management interface. (Server and JVM metrics can still be pulled from the management endpoint if the base
metricssubsystem is configured.)
We’ve also added support for MicroProfile Telemetry via a new
We’ve removed support for MicroProfile Metrics, except for a stub system limited to 'admin-only' mode that’s been kept to facilitate configuration migration. MicroProfile Metrics users are encouraged to use the new
We’ve removed support for MicroProfile OpenTracing, except for a stub system limited to 'admin-only' mode that’s been kept to facilitate configuration migration. MicroProfile OpenTracing users are encouraged to use the new
microprofile-telemetry-smallryesubsystem, or the
opentelemetrysubsystem upon which it is based.
Besides the changes in the observability space noted above, there are a couple of important changes in WildFly 28’s MicroProfile support:
We’ve added support for MicroProfile LRA via new
Except for MicroProfile Metrics and OpenTracing, which have been removed, we’ve updated our support for the other MicroProfile Platform specifications to the MicroProfile Platform 6 versions.
We’ve added a new
ee-core-profile-serverGalleon layer to make it easy to provision a server based on the new Jakarta EE Core Profile introduced in EE 10.
Related to this we’ve introduced new
servletGalleon layers. These layers allow a more tailored configuration compared to the existing
The server kernel team has added support for configuration customization using YAML. To learn more, see the article Emmanuel Hugonnet wrote last year about a preview version of this feature. (This feature is now available by default; there is no longer any need to perform the activation step described in the article.) YAML-based configuration customization is a nice alternative to using CLI scripts to tailor a stock configuration for a particular environment, as there is no need start a CLI process to apply the customization. This makes it well suited to workflows like deploying WildFly using Ansible.
The clustering team has added support for Infinispan query, counters, locks, and CDI.
The clustering and web teams have added support for configuration of an arbitrary cookie to use for web request affinity.
The RESTEasy team has added support for including request tracing information in HTTP response headers.
messaging-activemqsubsystem now supports integrating an SSLContext provided by the
When you use OIDC, the security team has added support for identity propagation from a WAR to an EJB in an EAR.
The web team has added default values for the
write-timeoutsettings for Undertow listeners.
We’ve updated Hibernate ORM from the ORM 6.1 release to 6.2.0.CR4.
The full release notes for the release are in the WildFly JIRA. Issues fixed in the numerous underlying WildFly Core 20.0 beta releases are listed in the WildFly Core JIRA.
Please try it out and give us your feedback, while we get to work on WildFly 28 Final! Our goal is for that to be available in mid April.