May 2026 - wildfly-dev - Jboss List Archives

Promote MCP server features to default stability level

by Jean-Frederic Mesnil

Hi, I’ve created a new issue to promote MCP server features to default stability level[1]. The intent is to make WildFly a MCP server where users could integrate their applications as MCP server resources (tools, resources) and open them to AI ecosystem. The scope is narrow and focuses only on MCP server features. The code has been in development for quite some time and we are in the process of implementing the latest MCP server specification. As part of this promotion, we need to iron out the code, fill gaps in the testing, provide documentation, etc. as described in our feature process document[2]. Only features and packages of the WildFly AI feature pack that provides MCP server capabilities are planned to move to default stability level. There are many other capabilities (including MCP client, LLM, WASM) provided by the feature pack that will remain at the experimental level. Best regards, Jeff [1] https://github.com/wildfly/wildfly-proposals/issues/829 [2] https://docs.wildfly.org/wildfly-proposals/FEATURE_PROCESS.html -- Jeff Mesnil Software Engineer Red Hat JBoss EAP http://jmesnil.net/ IBM Unless otherwise stated above: Compagnie IBM France Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex RCS Nanterre 552 118 465 Forme Sociale : S.A.S. Capital Social : 664 614 175,50 € SIRET : 552 118 465 03644 - Code NAF 6203Z

2 months, 3 weeks

2
5
0 / 0

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

3 months, 1 week

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:2.x

by thofman＠redhat.com

3 months, 1 week

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

3 months, 1 week

1
0
0 / 0

Re: Possible component upgrades report: Apache CXF 4.1.5/JBoss WS CXF 7.4.0 - wildfly:main

by Brian Stansberry

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. https://gist.github.com/bstansberry/d49c930a055a067ba99442788331b07b 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(a)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] > > https://wildfly.zulipchat.com/#narrow/channel/174184-wildfly-developers/t... > > --- > Fabio Burzigotti > Software Developer > IBM Software > fburzigo(a)ibm.com > > 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(a)lists.jboss.org > To unsubscribe send an email to wildfly-dev-leave(a)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

3 months, 1 week

2
1
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

3 months, 1 week

1
0
0 / 0

[SPAM] Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

3 months, 2 weeks

3
3
1 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

3 months, 2 weeks

1
0
0 / 0

[WFCORE-7565] Proposal for ACME External Account Binding support

by Charlie Zhang

Hello, I have opened a PR proposal for WFCORE-7565 to add support for ACME External Account Binding (EAB) configuration to the Elytron ACME client at preview stability. The proposal adds optional management model attributes for configuring the EAB key identifier and HMAC key on the Elytron certificate-authority-account resource. These values would then be passed into the Elytron ACME account creation flow so WildFly can interoperate with certificate authorities that require EAB. Proposal PR: - https://github.com/wildfly/wildfly-proposals/pull/831 Related issues: - https://issues.redhat.com/browse/WFCORE-7565 - https://issues.redhat.com/browse/ELY-2951 Feedback on the proposal, naming, and implementation approach would be appreciated. Thanks, Charlie Zhang

3 months, 2 weeks

1
0
0 / 0

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

3 months, 2 weeks

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev May 2026