Re: WildFly Community Call: November 27th (WildFly and AI)
by Tom Jenkinson
Just to mention that we are going to move this event to the week after - thank you for your understanding and hope to see you one week later!
________________________________
From: Tom Jenkinson
Sent: 18 November 2025 17:47
To: WildFly dev <wildfly-dev(a)lists.jboss.org>
Subject: WildFly Community Call: November 27th (WildFly and AI)
Hi,
You are very welcome to join us for next weeks WildFly Community Call. Among our usual topics, you can look forward to a very interesting topic shared by Emmanuel Hugonnet on the WildFly AI feature pack. If you have been interested to know how to work with AI and Jakarta EE in WildFly then please come along and ask any questions you might like to in our community group call.
Please find the agenda at https://docs.google.com/document/d/1kjaMGFGtL3MPY58UCJMojLlTzl335DUm1L-P9... and please find the event in our team calendar available via https://www.wildfly.org/events/
You can also find the event mentioned at:
https://www.linkedin.com/events/7396600116343750656/
https://x.com/WildFlyAS/status/1990836345929879619
Hope to see many of you there!
Unless otherwise stated above:
IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN
11 months
Testcontainers and ci.wildfly.org
by Brian Stansberry
A few days ago we started having a bunch of ci.wildfly.org failures in
tests that use Testcontainers. It seems something in testcontainers is
incompatible with the current release of Docker[1], so when Docker
gets updated things break. Docker was routinely updated on
ci.wildfly.org a few days ago and boom...
Ken Wills implemented a global workaround for this yesterday. We want
to remove that workaround tomorrow unless someone asks in this thread
for more time to adapt anything they are running.
The permanent fix is to update to Testcontainers 2.0.2, which they
released yesterday. We did that for the main branch in wildfly/wildfly
and we *think* that's the only thing currently using testcontainers on
ci.wildfly.org. But if we're wrong and you need more time before the
workaround is removed, please speak up.
[1] https://github.com/testcontainers/testcontainers-java/issues/11212
Best regards,
Brian
11 months
WildFly JUnit Extension and Tooling
by James Perkins
Hello All,
In some free time, I created a new project for WildFly i'm calling
wildfly-testing-tools [1]. Currently this includes a JUnit Extension for
managing a WildFly instance for tests. Please note this is NOT a
replacement for Arquillian. This is aimed for cases that are much more
simple than what Arquillian can handle.
This could end up being used in WildFly Core as a replacement for the JUnit
4 TestRunner we have. The idea for this project came from me wanting to
migrate the wildfly-maven-plugin to use JUnit 6. I needed a replacement for
a simple test runner that is similar to what we have in WildFly Core, so I
created this :)
I also moved some things from WildFly Arquillian into this project. The
reason being these were useful testing tools, but really don't have
anything to do with Arquillian. These extensions can be used with or
without Arquillian.
I'd like to propose we make this a WildFly project. I'd like others to have
a look and let me know if they would find it useful. I don't think it's
something we want to bring into WildFly testing itself, but I can see it
being useful for WildFly Core or projects where Arquillian might be a bit
of an overkill.
[1]: https://github.com/jamezp/wildfly-testing-tools
James R. Perkins
Principal Software Engineer
11 months
