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.
An overview of the Java Batch Processing API and JBeret implementation.Read More >
This video explains how to add upstream repositories, rebase onto upstream branches, and resolve merge conflicts in Git.Watch Video >
Reasons to get involved with the Jakarta EE Specification teams You are a developer that uses the WildFly (Jakarta EE) application server to create/update applications that meet your users needs. Reason #1 is to participate in developing future Jakarta EE releases. From adding a new feature to a specification, to implementing that new feature. You can also help by adding TCK tests for new features as well. Whether you contribute a small or large amount...Read More >
In this article, we give an update on changes made to the WildFly Docker images to enhance their capabilities. Thanks to contributions from Henri-Laiho and Kris-Gerhard, we have updated the images to use the JDK images from Eclipse Temurin as their base images. This provides the following highly requested capabilities: Provides multiarch images. The WildFly images now support linux/arm64 in addition to linux/amd64 Supports Long-Term Support (LTS) JDK 11 & 17 Supports the latest non-LTS...Read More >
An overview of the new support for filesystem realm integrity verification.Read More >
Bootable JAR Maven plugin 8.1.0 has been released.Read More >
A new distributed Jakarta Enterprise Bean TimerService for WildFlyRead More >
It gives me tremendous pleasure to announce that the new WildFly and WildFly Preview 27.0.0.Final releases are available for download at https://wildfly.org/downloads. Jakarta EE 10 Support For sure the biggest new thing in WildFly 27 is support for Jakarta EE 10. WildFly 27 is a compatible implementation of the EE 10 Platform as well as the Web Profile and the new Core Profile. WildFly is EE 10 compatible when running on both Java SE 11...Read More >