...

...

We want to inform our user community that WildFly support will be phased out after the release of Domibus 5.2. This decision comes after careful consideration of WildFly's limited usage among users and its is linked to limited usage of the Domibus WildFly edition and the application server’s lack of long-term support.

...

Despite its capabilities, WildFly has a short-term support cycle. Additionally, its usage among Domibus users has been limitedvery few users rely on it for operating Domibus.

To ensure Domibus remains installations remain robust, secure and up-to-date, we have decided to focus on application servers that offer long-term support and wider adoption. By . Further, by phasing out WildFly, we can better allocate our resources to improve Domibus on platforms that are more widely used and supported.

...

• Domibus 5.2 will support WildFly 34.0.x : The upcoming Domibus release (or future versions for 5.2.x patches released in the ensuing two-year period): This upcoming Domibus product line will be the last version one to include support for WildFly.
• Transition period: Domibus 5.2 is a long-term supported release. If you are using WildFly, this gives you at least two years to transition to another supported platform.
• Alternative platforms: We recommend moving from WildFly to one of the following platforms:
  • Oracle WebLogic Server: A robust application server with long-term support.
  • Apache Tomcat: A widely used, lightweight web server ideal for running Java applications.

...

If discontinuing WildFly support presents significant insurmountable challenges for your operations, please reach out to us. Your feedback will help us assess the need for additional support or transition time.

...