Thanks for your feedback Brian!
I'll look into the list of components you shared and try to address your questions and hints.

Meanwhile, I am sending an update about the possible component upgrades. 
I'm using my registered account this time, so sorry if that causes any confusion.

I generated this follow-up report after releasing the "Final" version for all the components in the upgrade, which is tracked by the following Jira issues:

- https://redhat.atlassian.net/browse/WFLY-21935 
- https://redhat.atlassian.net/browse/WFLY-21936

TL;DR - org.apache.cxf:* will be upgraded to 4.1.6, since 4.2.0 does not support JDK 11 (planned for jbossws-cxf-8.0.0).
The relevant upgrades are the following ones:

- Minor upgrades
        jboss.jaxbintros:jboss-jaxb-intros:2.0.1 -> Minor upgrade 2.1.0.Final
        org.jboss.ws:jbossws-api:3.0.0.Final -> Minor upgrade 3.1.0.Final
        org.jboss.ws:jbossws-common:5.1.0.Final -> Minor upgrade 5.2.0.Final
        org.jboss.ws:jbossws-common-tools:2.1.0.Final -> Minor upgrade 2.2.0.Final
        org.jboss.ws:jbossws-spi:5.0.0.Final -> Minor upgrade 5.1.0.Final
        org.jboss.ws.cxf:jbossws-cxf-client:7.3.8.Final -> Minor upgrade 7.4.0.Final

    Major upgrades
        org.jboss.ws.projects:jaxws-undertow-httpspi:2.0.0.Final -> Very latest 3.0.1.Final (a de-facto minor upgrade, as the exposed API didn't change)



On Fri, May 22, 2026 at 3:37 PM Brian Stansberry via wildfly-dev <wildfly-dev@lists.jboss.org> wrote:
Great; thanks, Fabio.

Looking at the weekly Possible Component Upgrades report we're behind on a lot of minors, and I wonder if this CXF / JBossWS upgrade will let us clear some of those. (I'm doing a bit of a general drive re this; this webservices aspect is just a well-timed piece. :))

I did a bit of 'git grep'ping sparked by the May 13 report and then did a bit of research into some (but not all) of the ones I grepped. The grepping is to figure out how things are used.


Going through that...

1) It looks like the CXF update lets us update woodstox.

2) We need to research guava. One of the uses is opensaml.

3) We seem to be using the istack version that the only lib that depends on it uses, so that seems ok, if you don't want to update.

4) We need to decide about commons.codec, which WS stuff uses, + others. We are behind what Artemis uses.

5) commons.collections is used by WS. We are actually on the latest version of the 3.x series, so this seems ok. There's a 4 series but I have no clue regarding compatibility. I believe the groupId changed.

6) Can we update opensaml?

7) Can we update joda-time? (We'll need to check the Hibernate Validator use as well -- Jason Lee... ping!)

Best regards,
Brian



On Fri, May 22, 2026 at 8:16 AM Fabio Burzigotti via wildfly-dev <wildfly-dev@lists.jboss.org> wrote:
Hi all, 
  Following up on a discussion on Zulip [1], I am attaching a report that previews the component upgrades coming with the consolidation and release of jbossws-cxf-7.4.0.Final.

TL;DR - org.apache.cxf:* will be upgraded to 4.1.5, since 4.2.0 does not support JDK 11 (planned for jbossws-cxf-8.0.0).
The relevant upgrades are the following ones:

  • Minor upgrades
    • Jboss.jaxbintros:jboss-jaxb-intros:2.0.1 -> Minor upgrade 2.1.0.Beta1 
    • org.jboss.ws:jbossws-api:3.0.0.Final -> Minor upgrade 3.1.0.Beta1
    • org.jboss.ws:jbossws-common:5.1.0.Final -> Minor upgrade 5.2.0.Beta1
    • org.jboss.ws:jbossws-common-tools:2.1.0.Final -> Minor upgrade 2.2.0.Beta1
    • org.jboss.ws:jbossws-spi:5.0.0.Final -> Minor upgrade 5.1.0.Beta1
    • org.jboss.ws.cxf:jbossws-cxf-client:7.3.8.Final -> Minor upgrade 7.4.0.Beta*

  • Major upgrades
    • org.jboss.ws.projects:jaxws-undertow-httpspi:2.0.0.Final -> Very latest 3.0.0.Beta  (a minor as a matter of fact, because the exposed API didn't change)

As you can see, all of them are currently released as Beta versions, and will be finalized as soon as testing is complete.

The plan is to finalize the component upgrade PR for WildFly within tomorrow/Monday.
I'll post an update as soon as Final versions are released.

Regards,
Fabio.

[1]

---
Fabio Burzigotti
Software Developer
IBM Software

IBM
Unless otherwise stated above:

IBM Italia S.p.A.
Sede Legale: Circonvallazione Idroscalo - 20054 Segrate (MI)
Cap. Soc. euro 247.656.998.20
C. F. e Reg. Imprese MI 01442240030 - Partita IVA 10914660153
Società con unico azionista
Società soggetta all'attività di direzione e coordinamento di International Business Machines Corporation
_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives:


--
Brian Stansberry
Collaborative Partner - IBM
Architect, JBoss EAP
WildFly Project Lead
He/Him/His
_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives:


--

Fabio Burzigotti
IBM Middleware