WildFly Project News
Introduction Now that WildFly supports Eclipse Microprofile this seems the appropriate time to introduce a way to package a WildFly application as a bootable JAR (also known as a "fat JAR"). Bootable JAR packaging is well suited for microservices to be run on cloud and bare metal. A bootable JAR allows us to package both the container and the application in a single JAR file and execute it with a simple command such as...
WildFly 20 S2I Docker images The WildFly S2I (Source-to-Image) builder and runtime Docker images for WildFly 20 have been released on quay.io/wildfly. Changes since the last release: Upgraded Keycloak client adapters to version 10.0.2. Reduced the size of the image generated during s2i chained build template (image named <app>-build-artifacts). For a complete documentation on how to use these images using S2I, OpenShift and Docker, refer to the WildFly S2I README. Adding the imagestreams and...
I’m pleased to announce that the WildFly 20 Final zip is now available for download. After the big push on Eclipse MicroProfile 3.3 for WildFly 19, the focus for WildFly 20 was more on bug fixing and component updates. Between WildFly Core and full WildFly we resolved well over 100 bugs and did over 90 component upgrades, most of which also brought bug fixes. These are challenging times for all of us, with a...
Using JBoss Generic JMS Resource Adapter you can use a JMS compatible client to connect WildFly to any broker. This article will describe how to do this with Apache Qpid and thus use JMS over AMQP. Installing Apache Qpid You need to download and untar Apache Qpid Broker-J 8.0.0 from https://qpid.apache.org/download.html. You need to allow for anonymous access. Please use the initial-config.json configuration file. Note that we will start Apache Qpid HTTP server on...
WildFly 19.1.0 Final is now available for download. As we usually do between WildFly majors, we’ve done an update release to provide the WildFly community with important bug fixes and component upgrades that have become available. Typically these are micro releases, but this time we had one feature that we wanted to make available, so we changed the version to 19.1.0 and released a minor. The feature is related to handling of SameSite cookie...
Introduction The standard and recommended way to configure the WildFly cloud images is by using environment variables. However, you could find it useful for your use case to configure the server by using a custom CLI management operations script. The following post describes how you can apply management operations to configure the WildFly server image. We will show you how you can execute CLI scripts at the Source-to-Image (S2I) phase and how to use...
WildFly 19 S2I Docker images The WildFly S2I (Source-to-Image) builder and runtime Docker images for WildFly 19 have been released on quay.io/wildfly. Changes since the last release: Optimized startup. The server starts much faster, as the CLI script applied to the server configuration is now executed during server boot. Support for clustering. JGroups is now part of the default server configuration. The WildFly 19 Galleon decorator layer web-clustering (support for Infinispan-based web session clustering)...
Until WildFly 19 you could use Eclipse MicroProfile OpenTracing (MPOT) to trace your application using environment variables relying on the SmallRye OpenTracing implementation. With WildFly 19 you can now configure several Jaeger Tracers to be used in your applications. Installing Jaeger Let’s start a jaeger instance using docker : docker run -d --name jaeger \ -p 6831:6831/udp \ -p 5778:5778 \ -p 14268:14268 \ -p 16686:16686 \ jaegertracing/all-in-one:1.16 Now, you can navigate to http://localhost:16686...
I’m pleased to announce that the WildFly 19 Final zip is now available for download. Work on WildFly 19 has been a long and exciting journey, with tremendous help from contributors in the community, a lot of support from the communities behind the components we integrate (particularly the Smallrye folks) and crucial backing from many of my colleagues at Red Hat, particularly all the QE folks who helped make sure all the new goodies...
I’m pleased to announce that with today’s WildFly 19.0.0.Beta3 release WildFly supports the Eclipse MicroProfile 3.3 platform specifications! The WildFly 19 Beta3 zip is now available for download. With the January release of WildFly 19 Beta1 we added support for MicroProfile 3.2. Since the MicroProfile 3.3 release was coming in February and the delta from 3.2 wasn’t too extreme we decided to go ahead and delay WildFly 19 a bit and go for MicroProfile...
