Skip to content

Fix typos in WildFly 42 release announcement #960

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bstansberry merged 1 commit into from
Oct 22, 2026
+6 −6
Merged

Fix typos in WildFly 42 release announcement #960

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions content/posts/2026-10-22-WildFly42Released.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,11 @@ The 42 release includes a number of new things:

* We now support use of https://redhat.atlassian.net/browse/WFLY-19563[virtual threads in Jakarta Concurrency resources, window=_blank].

* Configuration of idle-time-based eviction for distributable HttpSessions, SFSBs, and EJB timers has been https://docs.wildfly.org/wildfly-proposals/clustering/infinispan/WFLY-21526_Promote_idle_time-based_eviction_to_default_stability.html[promoted to `default` stability, window=_blank].
* Configuration of idle-time-based eviction for distributable HttpSessions, SFSBs, and EJB timers has been https://docs.wildfly.org/wildfly-proposals/clustering/infinispan/WFLY-21526_Promote_idle_time-based_eviction_to_default_stability.html[promoted to `default` stability, window=_blank].

* You can now optionally https://docs.wildfly.org/wildfly-proposals/elytron/WFCORE-7301-expose-a-new-attribute-on-the-token-realm-to-supply-a-principal-transformer-to-the-realm.html[transform the Principal obtained from a JWT when using a `token-realm`, window=_blank] by configuring use of a principal transformer, such as a `case-principal-transformer`, before the Principal is passed to the application being secured. This is provided at `community` stability.

* We've also unveiled major progress on https://redhat.atlassian.net/browse/WFLY-17851[SBOM generation, window=_blank] . A WildFly installation now includes a `sbom.cdx.json.gz` file at the root of the installation that provides CycloneDX format information about the software present in the installation. This file is produced by our Galleon provisioning tooling as part of provisioning the installation. For users who use our tooling to provision slimmed servers, its contents are limited to what was actually provisioned, excluding artifacts that are present in a complete WildFly installation but are not in your slimmed installation.
* We've also unveiled major progress on https://redhat.atlassian.net/browse/WFLY-17851[SBOM generation, window=_blank]. A WildFly installation now includes a `sbom.cdx.json.gz` file at the root of the installation that provides CycloneDX format information about the software present in the installation. This file is produced by our Galleon provisioning tooling as part of provisioning the installation. For users who use our tooling to provision slimmed servers, its contents are limited to what was actually provisioned, excluding artifacts that are present in a complete WildFly installation but are not in your slimmed installation.

[NOTE]
====
Expand All @@ -53,8 +53,8 @@ Evidence demonstrating our compatibility is available in the link:https://github
| link:https://github.com/wildfly/certifications/blob/EE11/WildFly_42.0.0.Final/jakarta-web-profile-jdk17.adoc#tck-results[SE 17, window=_blank]
| link:https://github.com/wildfly/certifications/blob/EE11/WildFly_42.0.0.Final/jakarta-web-profile-jdk21.adoc#tck-results[SE 21, window=_blank]
.2+.<| EE 11 Core Profile
| link:https://github.com/wildfly/certifications/blob/EE11/WildFly_42.0.0.Final/jakarta-core-jdk17.adoc#jakarta-core-profile-1001-tck-java-se-17-results[SE 17, window=_blank]
| link:https://github.com/wildfly/certifications/blob/EE11/WildFly_42.0.0.Final/jakarta-core-jdk21.adoc#jakarta-core-profile-1001-tck-java-se-21-results[SE 21, window=_blank]
| link:https://github.com/wildfly/certifications/blob/EE11/WildFly_42.0.0.Final/jakarta-core-jdk17.adoc#tck-results[SE 17, window=_blank]
| link:https://github.com/wildfly/certifications/blob/EE11/WildFly_42.0.0.Final/jakarta-core-jdk21.adoc#tck-results[SE 21, window=_blank]
|=======================================================================


Expand All @@ -73,7 +73,7 @@ For the MicroProfile 7.1 specifications where WildFly 42 is compatible, link:htt
With the 42 release, WildFly Preview has taken its first steps toward implementing the upcoming EE 12 specifications. WildFly Preview now provides:

* https://jakarta.ee/specifications/cdi/5.0/[Jakarta Contexts and Dependency Injection 5.0, window=_blank]
* The `3.1.0-M2` milestone release of the upcoming https://jakarta.ee/specifications/jsonb/3.1/[Jakarata JSON Binding 3.1, window=_blank].
* The `3.1.0-M2` milestone release of the upcoming https://jakarta.ee/specifications/jsonb/3.1/[Jakarta JSON Binding 3.1, window=_blank].

WildFly Preview 42 implements the same version of other standards as standard WildFly.

Expand Down Expand Up @@ -108,7 +108,7 @@ The WildFly project plans to move its baseline Java SE version to SE 21 for next

There are some behavioral changes in WildFly 42 that may affect some users:

* WildFly 42's `jgroups` subsystem will log WARN messages if JGroups channels are started without protocols in their protocol stack that provide authentication (e.g. `AUTH`) and encryption (e.g. `ASYM_ENCRYPT` or `SYM_ENCRYPT`). Use of authentication and encryption protocols are important steps in ensuring intra-cluster communications are secure. WildFly's out-of-the-box configuration do not include these protocols, because their use requires installation-specific settings. In the future we may choose to require these protocols to be present and to accept that our out-of-the-box HA configurations will not be able to boot unmodified.
* WildFly 42's `jgroups` subsystem will log WARN messages if JGroups channels are started without protocols in their protocol stack that provide authentication (e.g. `AUTH`) and encryption (e.g. `ASYM_ENCRYPT` or `SYM_ENCRYPT`). Use of authentication and encryption protocols is an important step in ensuring intra-cluster communications are secure. WildFly's out-of-the-box configurations do not include these protocols, because their use requires installation-specific settings. In the future we may choose to require these protocols to be present and to accept that our out-of-the-box HA configurations will not be able to boot unmodified.
* The https://github.com/eclipse-ee4j/yasson[Eclipse Yasson, window=_blank] project that WildFly uses internally and includes in our https://central.sonatype.com/artifact/org.wildfly/wildfly-standard-ee-bom/42.0.0.Final[user boms, window=_blank] changed its Maven groupId from `org.eclipse` to `org.eclipse.yasson` in their 3.0.5 release. They set up Maven redirects, so resolution using the old groupId should still work.


Expand Down
Loading