WildFly 28 is released!

I’m pleased to announce that the new WildFly and WildFly Preview 28.0.0.Final releases are available for download at https://wildfly.org/downloads.

New and Notable

Observability

The biggest changes in WildFly 28 relate to the observability space.

MicroProfile

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 microprofile-lra-coordinator and microprofile-lra-participant subsystems.

  • 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.

Because we no longer support MicroProfile Metrics, WildFly 28 cannot claim to be a compatible implementation of the MicroProfile 6.0 specification. However, WildFly’s MicroProfile support includes implementations of the following specifications in our "full" (e.g. standalone-full.xml) and "default" (e.g standalone.xml) configurations as well as our "microprofile" configurations (e.g. standalone-microprofile.xml):

MicroProfile Technology WildFly Full/Default Configurations WildFly MicroProfile Configuration

MicroProfile Config 3.0

X

X

MicroProfile Fault Tolerance 4.0

 — 

X

MicroProfile Health 4.0

 — 

X

MicroProfile JWT Authentication 2.1

X

X

MicroProfile LRA 2.0

 — 

X

MicroProfile OpenAPI 3.1

 — 

X

MicroProfile Open Telemetry 1.0

 — 

X

MicroProfile Reactive Messaging 3.0

 — 

 — 

MicroProfile Reactive Streams Operators 3.0

 — 

 — 

MicroProfile Rest Client 3.0

X

X

Provisioning

Also, separate from WildFly itself, to help users in their migration from Jakarta EE 8 to EE 10 we’ve introduced a separate WildFly Extras project that provides a new Galleon feature pack. The wildfly-deployment-transformer-feature-pack allows you to integrate into a standard WildFly installation the EE 8 to EE 9 deployment transformation functionality that we’ve provided in WildFly Preview since its first release. See the wildfly-deployment-transformer-feature-pack README for documentation on how to use this new feature pack.

Quickstarts

Other Treats

Jakarta EE 10 Support

WildFly 28 is a compatible implementation of the EE 10 Platform as well as the Web Profile and the new Core Profile. WildFly is EE 10 compatible when running on both Java SE 11 and Java SE 17.

Evidence supporting our certification is available in the WildFly Certifications repository on GitHub:

Java SE Support

Our recommendation is that you run WildFly on the most recent long-term support Java SE release, i.e. on SE 17 for WildFly 28. While we do do some testing of WildFly on JDK 20, we do considerably more testing of WildFly itself on the LTS JDKs, and we make no attempt to ensure the projects producing the various libraries we integrate are testing their libraries on anything other than JDK 11 or 17.

WildFly 28 also is heavily tested and runs well on Java 11. We plan to continue to support Java 11 at least through WildFly 29, and likely beyond. We do, however, anticipate removing support for SE 11 sometime in the next 12 to 18 months.

While we recommend using an LTS JDK release, I do believe WildFly runs well on JDK 20. By runs well, I mean the main WildFly testsuite runs with no more than a few failures in areas not expected to be commonly used. We want developers who are trying to evaluate what a newer JVM means for their applications to be able to look to WildFly as a useful development platform.

Please note that WildFly runs on Java 11 and later in classpath mode.

Known Issues

Spring and RESTEasy Spring

In WildFly 27, pending the final release of Spring 6, RESTEasy Spring support was removed from standard WildFly, and was only provided with WildFly Preview. With WildFly 28 we have reintroduced RESTEasy Spring support to standard WildFly.

However, we’ve learned of a bug in WildFly 28 that will prevent Spring deployments, including those using RESTEasy Spring, from working. Until this is resolved in WildFly 28.0.1, users can work around this issue by adding a jboss-deployment-structure.xml file to their deployment that declares a dependency on the org.jboss.vfs module.

Release Notes

The full release notes for the release are in the WildFly JIRA. Issues fixed in the underlying WildFly Core 20.0.0 and 20.0.1 releases are listed in the WildFly Core JIRA.

Please try it out and give us your feedback, while we get to work on WildFly 29!

Best regards,

Brian