WildFly Community Call - 2025-11-13

13 views

Skip to first unread message

jme...@redhat.com

unread,

Nov 17, 2025, 3:16:38 AM (12 days ago) Nov 17

to WildFly

Hi, we held a WildFly Community call on Thursday, November 13th.

Recording can be watched at https://www.youtube.com/watch?v=OgJti-R_wDk&t=1091s

As a reminder this call is open to any community members -- users and developers alike (the meetings are in our WildFly calendar at https://www.wildfly.org/events/#calendar

Please find below the agenda of the call:

Week 46 (2025-11-13)

📺 YouTube video

Community Announcements (:00)

WildFly 38.0.1.Final release
- Delayed due to infrastructure issues

Agenda (:10)

Brian Stansberry & Wolfgang Knauf | Maven Archetypes for WildFly
- wildfly-archetypes PRs. Decide what to do with the 2 long-standing open PRs
  Current state:
  - getting-started: during build, a wildfly server is provisioned including the war file. Tests are executed using Arquillian. There are 2 types of tests:
    - “Close-box” test that @RunAsClient and communicates with the actual war file ApplicationIT.java
    - “Open-box” test that creates an enriched war (with only the classes under tests) and run the test inside this enriched war (eg to access CDI components directly) ServiceIT.java#L24
  - webapp/ear archetype: during build a war / ear file is created in “target”. Two profiles are used to execute the tests with “wildfly-arquillian-container-managed” or “wildfly-arquillian-container-remote”. Both profiles require an installed wildfly server, the arquillian container launches tests by creating an enriched war / ear file and deploying it to this server.

Proposed enhancement in webapp/ear archetype:

New profile “provision”: provisions a wildfly server that contains the war/ear application.
New profile “arq-provision”: also provisions a wildfly server (but without deployed war), then start this server by using “wildfly-arquillian-container-managed”, enrich the war file with tests, deploy it to server and run the arquillian tests.

Discussion: is this too much for a single archetype? Should the old profiles be cleaned up? Should some interactive part be added when creating a project from the archetype so that some features of it (arquillian/provisioning/faces support) can be skipped?

Related to the Maven archetypes, we could extend the subsystem archetype (or create another archetype) to help development of new Galleon feature pack (reported in [wildfly/wildfly-archetypes#185] gProvide an archetype for WildFly feature packs )

FYI about interesting discussions
- Brian Stansberry Classloading of optional modules (new today; I haven't read it beyond the first few posts...)
- Brian Stansberry JPMS for Modules This is about a bunch of lower priority issues I filed Tuesday re adding module-info.class to various components. These are background tasks to help be ready for a future where Java SE is more insistent on using JPMS.

Parking lot (:45)

Next meeting, Emmanuel Hugonnet will present the Generative AI feature pack for WildFly (Langchain4J, MCP, WASM)