The release has been published WildFly 40 — a free Java application server developed by the WildFly community with the participation of Red Hat. Simultaneously, builds have been prepared wildfly, WildFly EE 10 и WildFly Preview 40.0.0.Final; Galleon extension packages for the new version are hosted on Maven Central. The project's source code is distributed under a license Apache License 2.0.
The main change in WildFly 40 was the transfer of the standard edition of the server to Jakarta EE 11Support for EE 11 was previously developed in WildFly Preview starting with the WildFly Preview 32 branch, and has now been migrated to the regular WildFly edition. Support is declared for the Jakarta EE 11 Platform, Web Profile, and Core Profile when running on Java SE 17 and Java SE 21.
Key changes in WildFly 40:
Support for Jakarta EE 11 in standard edition. WildFly has migrated to the latest EE 11 stack, including Jakarta Data, improvements to Jakarta Persistence 3.2, and support for virtual threads in Jakarta Concurrency when running on Java SE 21 and later. However, the developers recommend Java SE 25 for using virtual threads. For applications not yet ready for EE 11, a separate server variant with the Jakarta EE 10 API has been added. Non-EE-specific functionality remains common between the regular WildFly and WildFly EE 10.
Logging out of applications with OIDC. WildFly now supports logout for applications protected by OIDC, including RP-Initiated Logout, Front-Channel Logout, and Back-Channel Logout. This feature is currently at the preview stability level.
Improving the stability of existing functions. The dynamic SSLContext, which can select an SSL context based on the destination host and port, the custom AJP headers setting in Undertow, and the reverse proxy handler parameters for working with X-Forwarded and Host rewriting have been moved to the default level. Jakarta Data support in the default WildFly has been moved to the community level.
The release also includes a major dependency update. Notable releases include: Apache Artemis 2.53, Hibernate 7.3.2, Jackson 2.21.1, Micrometer 1.16, Netty 4.1.133, Undertow 2.4.0, Vert.x 4.5.24, WildFly Elytron 2.9.0, Elytron Web 4.2.0, WildFly Glow 2.0.0 и WildFly OpenSSL 2.3.0Some updates address known CVEs in Artemis, Jackson, Netty, Undertow, and Vert.x.
The developers have changed the Java version recommendations. For regular WildFly 40 and WildFly Preview 40, the recommended version is now JavaSE 25 as the current LTS release. For WildFly EE 10, it is recommended JavaSE 21, including due to the specifics of EE 10 compatibility testing and the dependence of some specifications on SecurityManager. All three WildFly 40 variants are actively tested and work on Java 25, 21, and 17, but support for Java SE 17 may be removed in a future release.
There are also changes that break backward compatibility. Regular WildFly and WildFly Preview no longer launch with the Java SecurityManager enabled, as EE 11 no longer supports it. Additionally, Apache Artemis has changed its Maven groupId from org.apache.activemq to org.apached.artemis, which may impact users of WildFly BOM files. The standard WildFly edition no longer supports the old EE ManagedBeans model with the @ManagedBean annotation when upgrading to EE 11; WildFly EE 10 retains this annotation.
Full List of changes The release notes have been published on GitHub, where resolved issues regarding WildFly 39 are also listed.
Source: linux.org.ru
