WildFly is a powerful, modular, & lightweight application server that helps you build amazing applications.
Configuration in WildFly is centralized, simple and user-focused. The configuration file is organized by subsystems that you can easily comprehend and no internal server wiring is exposed. All management capabilities are exposed in a unified manner across many forms of access. These include a CLI, a web based administration console, a native Java API, an HTTP/JSON based REST API, and a JMX gateway. These options allow for custom automation using the tools and languages that best fit your needs.
WildFly does classloading right. It uses JBoss Modules to provide true application isolation, hiding server implementation classes from the application and only linking with JARs your application needs. Visibility rules have sensible defaults, yet can be customized. The dependency resolution algorithm means that classloading performance is not affected by the number of versions of libraries you have installed.
WildFly takes an aggressive approach to memory management. The base runtime services were developed to minimize heap allocation by using common cached indexed metadata over duplicate full parses, which reduces heap and object churn. The administration console is 100% stateless and purely client driven. It starts instantly and requires zero memory on the server. These optimizations combined enable WildFly to run with stock JVM settings and also on small devices while leaving more headroom for application data and supports higher scalability.
WildFly implements the latest in enterprise Java standards from Jakarta EE and Eclipse MicroProfile. These improve developer productivity by providing rich enterprise capabilities in easy to consume frameworks that eliminate boilerplate and reduce technical burden. This allows your team to focus on the core business needs of your application. By building your application on standards you retain the flexibility to migrate between various vendor solutions.
A recap of Open Source Day, held during the virtual Grace Hopper Celebration.Read More >
For WildFly 25, we upgraded the MicroProfile Reactive Messaging support from version 1 to 2. It contains a new @Channel annotation, which in conjunction with the new Emitter interface, were introduced in order to make it possible to push data into the MicroProfile Reactive streams from code initiated by a user. The MicroProfile Reactive Messaing implementation in WildFly is based on the SmallRye Reactive Messaging project. The version included in WildFly 25, introduces a new...Read More >
WildFly 25 S2I Docker images The WildFly S2I (Source-to-Image) builder and runtime Docker images for WildFly 25 have been released on quay.io/wildfly. For complete documentation on how to use these images using S2I, OpenShift and Docker, refer to the WildFly S2I README. Important changes to mention in this release We have been evolving the s2i builder image to reflect part of the main changes that occurred in WildFly 25. In particular the s2i image content...Read More >
An overview of the WildFly Elytron project's participation in Hacktoberfest.Read More >
I’m pleased to announce that the WildFly 25 Final zip is now available for download. The big focus during the WildFly 25 development cycle has been on support for Java SE 17 and on the related transition away from our legacy security layer and to a purely WildFly Elytron-based security layer. More about those later, but first let’s look at new features in WildFly 25. New Features A new subsystem has been added that provides...Read More >
As significant changes percolate through the enterprise Java ecosystem, particularly progress on Jakarta EE 10 and the move to the jakarta.* namespace for the EE APIs, changes are also going to be coming to WildFly. In this post I want to describe what I see happening over the next few WildFly releases, starting with the WildFly 25 release that will be out soon. SE 17 and the WildFly security layer This month’s GA release of...Read More >
WildFly 25 Beta1 S2I Docker images The WildFly S2I (Source-to-Image) builder and runtime Docker images for WildFly 25 Beta1, have been released on quay.io/wildfly. For complete documentation on how to use these images using S2I, OpenShift and Docker, refer to the WildFly S2I README. Important changes to mention in this Beta release We have been evolving the s2i builder image to reflect part of the main changes that occurred in WildFly 25 Beta. In particular...Read More >