We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The upgrade to jaxb-runtime-4.0.3 introduced an incompatibility when the defaultNamespaceRemap property is used.
defaultNamespaceRemap
I have an executable example project here on GitHub to demonstrate the issue.
Until 4.0.2 the produced xml was using a namespace prefix:
<ns2:helloRequest xmlns:ns2=\"http://demo.ws.example.com\"><name>Klaus</name></ns2:helloRequest>
After the 4.0.3 upgrade the produced xml is as follows:
<helloRequest xmlns="http://demo.ws.example.com"><name>Klaus</name></helloRequest>
Caused by #1715.
The Web Service having the issue was using Apache CXF as a client talking to Spring Web Services on the server side.
Apache-CXF JAXBContextCache
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
The upgrade to jaxb-runtime-4.0.3 introduced an incompatibility when the
defaultNamespaceRemap
property is used.I have an executable example project here on GitHub to demonstrate the issue.
Until 4.0.2 the produced xml was using a namespace prefix:
<ns2:helloRequest xmlns:ns2=\"http://demo.ws.example.com\"><name>Klaus</name></ns2:helloRequest>
After the 4.0.3 upgrade the produced xml is as follows:
<helloRequest xmlns="http://demo.ws.example.com"><name>Klaus</name></helloRequest>
Caused by #1715.
The Web Service having the issue was using Apache CXF as a client talking to Spring Web Services on the server side.
Apache-CXF JAXBContextCache
The text was updated successfully, but these errors were encountered: