For several years now, WildFly has supported the ability to install and use different Jakarta Faces (Faces) implementations, either across every application deployed to the server, or for a specific application only. We supported running either Mojarra and MyFaces, with versions running all the way back to 1.2. With the move to Jakarta EE 10, however, that feature was temporarily broken simply because there was not a 4.0-compliant version of MyFaces available by the time we were ready to ship. That has changed now, though, as has the manner in which we support changing the implementations. In this short post, I'll show you how that works starting in WildFly 29.

With the release of WildFly 28 , we've made a few changes to our supported telemetry libraries that are worth noting. In this post, I'll give a quick overview of those changes.

Back again with another Testcontainers example. This time, though, the environment is a bit different. We'll be looking at a Jakarta EE application using WildFly and MicroProfile Reactive Messaging (MP RM), and we're going to test it using Arquillian and Testcontainers . Let's get to it. :)

I have written a few posts about using Quarkus with Testcontainers , Flyway , and jOOQ . Since posting those, I've learned some new tricks that have changed how I integrate the various tools. In this post, I'd like to share a complete example that shows how use Quarkus, Quarkus Dev Services , Testcontainers , and Flyway together for a zero (ish) local config setup.

A big part of the testing we do on WildFly involves in-container testing, for which we use Arquillian . It's a great tool when it works right, but sometimes things don't. When that happens, I find it helpful to examine the archives that the tests produce. Fortunately, Arquillian makes that easy if you know that magic words, and they're not easy to find, so I'm going to fix that here. :P