WildFly 27.0.1 is now available
WildFly is a powerful, modular, & lightweight application server that helps you build amazing applications.
Powerful
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.
Modular
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.
Lightweight
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.
Standards Based
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.
Latest News
The wildfly-maven-plugin has introduced a new dev goal. If you are familiar with the run goal, this goal is very similar. However, it watches for changes to source files. If changes are found, the WAR is rebuilt and redeployed. This new goal is available in version 4.1.0.Beta3 of the wildfly-maven-plugin. Using the dev Goal In its simplest form you enable the plugin like any other maven plugin: <plugin> <groupId>org.wildfly.plugins</groupId> <artifactId>wildfly-maven-plugin</artifactId> <version>${version.wildfly-maven-plugin}</version> </plugin> Once added to...
Read More >WildFly 26.1.3.Final is now available for download. We’ve received requests from members of our community to address a recent critical severity CVE in Apache CXF. The WildFly project generally doesn’t continue to produce bug-fix releases for older versions once a new major or minor release is out. But we recognize that the transition to WildFly 27 and EE 10 is likely to take our users longer than it does for most releases, so given the...
Read More >In this brief demonstration, we’ll set up and run three instances of WildFly on the same machine (localhost). Together they will form a cluster. It’s a rather classic setup, where the appservers needs to synchronize the content of their application’s session to ensure fail over if one of the instances fails. This configuration guarantees that, if one instance fails while processing a request, another one can pick up the work without any data loss. Note...
Read More >A recap of the Ask Me Anything session with the WildFly Elytron team that took place this week.
Read More >WildFly 27.0.1.Final is now available for download. It’s been about five weeks since the WildFly 27 release, so we’ve done a small bug fix update, WildFly 27.0.1. This includes an update to WildFly Preview. The following issues were resolved in 27.0.1: Bugs [WFLY-17186] - Wrong exception handling by ManagedScheduledExecutorService.schedule(…) [WFLY-17287] - Cannot persist ejb timers into database [WFLY-17313] - Distributed TimerService fails when cache is configured with jdbc-store [WFLY-17350] - Custom mail providers are not...
Read More >The WildFly Elytron team will be having an Ask Me Anything session on Monday Dec. 19th on chat.
Read More >This article provides details on the new S2I and runtime multi-arch images. New WildFly S2I and Runtime Multi-arch Images These new multi-arch images (linux/arm64 in addition to linux/amd64) have a different naming scheme than the current WildFly images to better handle multiple JDK versions and align with the tag scheme used for the WildFly centos7 docker images (as explained in Updates on WildFly Docker Images blog post). Note The previous WildFly images are now deprecated...
Read More >