WildFly Project News
WildFly 17 S2I image on quay.io Starting with WildFly 17, the WildFly S2I Docker image is now accessible from quay.io at this URL: https://quay.io/repository/wildfly/wildfly-centos7 A companion image, a WildFly runtime Docker image that allows you to chain builds in OpenShift or use Docker multi stage builds, is available from: https://quay.io/repository/wildfly/wildfly-runtime-centos7 For a complete documentation on how to use these images using s2i, OpenShift and Docker, refer to this documentation. WildFly 17 S2I image and the...
I’m pleased to announce that WildFly 17 Final is now available for download. A lot of effort in this last quarter has gone into using WildFly in cloud environments, which I’ll expand on more below, but first I wanted to touch on improvements we’ve made in the main WildFly server. Clustering Improvements You can now use a separate subsystem for configuring distributed web session managers. This will help users avoid common configuration mistakes, and is...
After HipChat got closed down earlier this year we evaluated a few alternative chat solutions. During this period we temporarily moved community discussions back to IRC (#wildfly on Freenode). We found that Zulip worked well for us and have now settled on this as our main chat tool. Thanks to the people at Zulip for their open source license! To join in, go to https://wildfly.zulipchat.com and sign up. The most obvious stream to join is...
Following the release of WildFly 16, I thought it would be a good time to give the WildFly community a sense of what I see coming in the project over the next few releases. WildFly will continue with the quarterly delivery model we began last year with WildFly 12. These releases are essentially time-boxed; i.e. we typically won’t significantly delay a release in order to get a feature in. So when I discuss general feature...