Lars Uffmann created CXF-8891:
---------------------------------
Summary: Evaluate changes to org.glassfish.jaxb:jaxb-runtime:4.0.3
Key: CXF-8891
URL: https://issues.apache.org/jira/browse/CXF-8891
Project: CXF
Issue Type: Task
Components: Core
Affects Versions: 4.0.2
Reporter: Lars Uffmann
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
{code:java}
<ns2:helloRequest
xmlns:ns2="http://demo.ws.example.com";><name>Klaus</name></ns2:helloRequest>{code}
With 4.0.3 it will become
{code:java}
<helloRequest
xmlns="http://demo.ws.example.com";><name>Klaus</name></helloRequest>{code}
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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
