Description
In the latest release of jaxb-runtime, 4.0.3, a change has been made which might affect CXF by introducing incompatibilities and/or interoperability issues.
The changes are related to the JAXB Context Property
org.glassfish.jaxb.defaultNamespaceRemap
https://github.com/eclipse-ee4j/jaxb-ri/issues/1715
For example, until 4.0.3, an XmlRootElement is marshaled as
<ns2:helloRequest xmlns:ns2="http://demo.ws.example.com"><name>Klaus</name></ns2:helloRequest>
With 4.0.3 it will become
<helloRequest xmlns="http://demo.ws.example.com"><name>Klaus</name></helloRequest>
In your parent pom, the version for jaxb-runtime is still 3.0.2. However, recent Spring boot versions >= 3.0.x are managing the 4.0.x version of jaxb-runtime. I stumbled over this issue after upgrading to the latest Spring Boot (3.0.8 / 3.1.1) release, which will upgrade the jaxb-runtime from 4.0.2 to 4.0.3.
I created an Issue in jaxb-ri as well:
https://github.com/eclipse-ee4j/jaxb-ri/issues/1724
Im not sure how this might affect cxf users. The web service affected by this issue is as simple as it can get and is used exclusively for integration testing purposes. A client using cxf could no longer talk to a server using spring web services.
Attachments
Issue Links
- is related to
-
CXF-8671 Support Jakarta EE 10
-
- In Progress
-