Skip to content

[Issue_930] Add the WildFly 42.0.0.Final release - #959

Merged
bstansberry merged 2 commits into
wildfly:mainfrom
bstansberry:rel42
Oct 22, 2026
Merged

bstansberry merged 2 commits into
wildfly:mainfrom
bstansberry:rel42

Conversation

@bstansberry

Copy link
Copy Markdown
Contributor

Resolves #930

@github-actions

Copy link
Copy Markdown

A preview of this PR is available at https://pr-959-wildfly-org.surge.sh

@bstansberry
bstansberry merged commit 90a584e into wildfly:main Oct 22, 2026
1 check passed
@bstansberry
bstansberry deleted the rel42 branch October 22, 2026 21:11
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].

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 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].


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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 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 are important steps in ensuring intra-cluster communications are secure. WildFly's out-of-the-box configuration does 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WildFly 42 release announcement

2 participants