[jira] [Created] (CXF-8891) Evaluate changes to org.glassfish.jaxb:jaxb-runtime:4.0.3
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}
http://demo.ws.example.com";>Klaus{code}
With 4.0.3 it will become
{code:java}
http://demo.ws.example.com";>Klaus{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)
[jira] [Resolved] (CXF-8865) Get rid of EasyMock in cxf-rt-management
[ https://issues.apache.org/jira/browse/CXF-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8865. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-management > > > Key: CXF-8865 > URL: https://issues.apache.org/jira/browse/CXF-8865 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.6.2, 4.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8891) Evaluate changes to org.glassfish.jaxb:jaxb-runtime:4.0.3
[
https://issues.apache.org/jira/browse/CXF-8891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-8891:
--
Fix Version/s: 4.1.0
> 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
>Priority: Major
> Fix For: 4.1.0
>
>
> 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}
> xmlns:ns2="http://demo.ws.example.com";>Klaus{code}
> With 4.0.3 it will become
> {code:java}
> xmlns="http://demo.ws.example.com";>Klaus{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)
[jira] [Commented] (CXF-8891) Evaluate changes to org.glassfish.jaxb:jaxb-runtime:4.0.3
[
https://issues.apache.org/jira/browse/CXF-8891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737407#comment-17737407
]
Andriy Redko commented on CXF-8891:
---
Thanks for heads up [~cachescrubber] , we've been planning to support JAXB 4.x
(Jakarta EE 10) in Apache CXF 4.1.0, see please
https://issues.apache.org/jira/browse/CXF-8671
> 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
>Priority: Major
>
> 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}
> xmlns:ns2="http://demo.ws.example.com";>Klaus{code}
> With 4.0.3 it will become
> {code:java}
> xmlns="http://demo.ws.example.com";>Klaus{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)
