WildFly Project News
This video demonstrates how to enable encryption for new filesystem realms, and how to encrypt pre-existing filesystem realms.
A demonstration on how to configure Elytron for secure connections to EJBs, using mutual TLS, SASL authentication mechanisms, and credential stores.
Another interview for our WildFly open source rockstars series.
This video demonstrates how you can configure TLS using the Let’s Encrypt certificate authority with the WildFly CLI.
WildFly 26.1.1.Final is now available for download. It’s been about five weeks since the WildFly 26.1 release, so we’ve done a small bug fix update, WildFly 26.1.1. This includes an update to WildFly Preview. The full list of issues resolved in WildFly 26.1.1 is available here. Issues resolved in the WildFly Core update included with WildFly 26.1.1 are available here. Note that the release artifacts are available in public maven in the jboss.org maven repo...
Today we have released a 27.0.0.Alpha1 version of WildFly Preview. This release serves as a milestone on our way toward support for Jakarta EE 10 in WildFly Preview, and eventually in standard WildFly. As discussed in my January WildFly Release Plans for 2022 post, the main focus of the WildFly developers as we work on WildFly 27 is implementing Jakarta EE 10 support. That work has now reached a point in WildFly Preview where it’s...
This video demonstrates how you can configure and deploy a Jakarta EE application that connects to a PostgreSQL database on OpenShift.
In addition to the WildFly zip download familiar to a lot of our users, a big part of the WildFly story is that it is very usable on the cloud. And of course for that we have a lot of tests, many of which are currently private. We now have a proof of concept public cloud testsuite which can be found at https://github.com/wildfly-extras/wildfly-cloud-tests. It does not aim to run the full testsuite from https://github.com/wildfly/wildfly/tree/main/testsuite. Rather,...
In WildFly the configuration is managed and stored in the standalone.xml. You have several ways to customize your configuration: edit the XML manually (which is not the recommended approach) or create jboss-cli scripts that you can run on each upgrade. So why propose a 'new' solution to customize a server configuration ? Well the idea was to be able to externalize the customization from the 'standard' provided configuration to facilitate server upgrades: just unzip the...
