WildFly Project News
The WildFly 10.0.0.Beta1 release includes support for an experimental new feature, that allows you to use JavaScript on the server side, using the Nashorn JavaScript engine that is built into the JDK. Combined with another new feature that allows you to serve web resources from outside the deployment it is possible to write server-side code with no redeploy of copy step involved. This feature also allows Java EE resources such as CDI beans to be...
The WildFly 10.0.0.Beta1 release is now available for download! Notable highlights include: Continued Java EE7 Support Java 8+ Required ActiveMQ Artemis JavaScript Support with Hot Reloading Offline CLI Support For Domain Mode HA Singleton Deployments Migration Operations for Legacy Subsystems Capabilities and Requirements Hibernate 5 Infinispan 8 These are covered in more detail on the official 10.0.0.Beta1 Release Notes wiki page
The ELK stack; elasticsearch, logstash and kibana can be used for centralize logging. It’s not the intention of this post to be a tutorial on how to configure logstash. We will go through a basic logstash configuration then configure WildFly to send log messages to logstash. Download and Configure logstash First we need to download logstash. Once the download is complete simply extract logstash from the archive. Next we will need to create a configuraton...
WildFly 9.0.1.Final and 8.2.1.Final are now available for download. These releases include security updates and bug fixes. For more details see the release notes for 8.2.1 here and 9.0.1 here.
The WildFly 9 Final release is now available for download! Java EE7 As with WildFly 8, WildFly 9 is a certified implemenation of both the Java EE7 full and web profile specifications. HTTP/2 Support Undertow, the web server in WildFly, has added support for the new HTTP/2 standard. HTTP/2 reduces latency by compressing headers and multiplexing many streams over the same TCP connection. It also supports the ability for a server to push resources to...
Once again, we’re delighted and enthralled to announce a release of WildFly Swarm. This time, it’s 1.0.0.Alpha3! Since this follows quickly on the heels of the last release, there’s not a whole lot of major changes. Rather, we’ve fixed some things, enhanced others, written some tests, and generally knocked it together a little sturdier. Changes Based on WildFly 9.0.0.CR2. You can now stop() the container. Better classloading for javax.* stuff. JPA improvements: Default datasources are...
I’m happy to announce the WildFly 9.0.0.CR2 release! This release addresses a number issues discovered during the CR1 cycle, and also includes a major UX update to the console. For those new to WildFly 9, it builds off of WildFly 8’s Java EE7 support, and adds many new capabilities, including intelligent load balancing, HTTP/2 support, a new offline CLI mode, graceful single node shutdown, and a new Servlet-only distribution. Provided no major issues are discovered,...
We’ve been churning through the improvements and fixes for Alpha2! Windows All the Windows issues are now resolved. You can enjoy the benefits of WildFly Swarm on your operating system of choice. Modify your Application from Alpha1 We’ve made a few changes to how the plugin works which means that you will need to update any applications that are already utilizing Alpha1: Remove the execution phase from the wildfly-swarm-plugin Change the goal of the wildfly-swarm-plugin...
Happy Cinco De Mayo! Crack open a cold adult beverage and start retooling your JavaEE skills towards microservices. What is WildFly Swarm? WildFly Swarm [1] is a new sidecar project supporting WildFly 9.x to enable deconstructing the WildFly AS and pasting just enough of it back together with your application to create a self-contained executable jar. JAX-RS is a microservice? In the simplest case, you make small adjustments to your existing Maven pom.xml that generates...
I’m happy to announce WildFly 9.0.0.CR1! WildFly 9 builds off of WildFly 8’s Java EE7 support, and adds many new capabilities, including intelligent load balancing, HTTP/2 support, a new offline CLI mode, graceful single node shutdown, and a new Servlet-only distribution. For more details, check out the full release notes. Provided no major issues are discovered, we plan to move to Final fairly quickly, sometime in May. Enjoy!