[
https://issues.apache.org/jira/browse/CXF-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906266#action_12906266
]
Benson Margulies commented on CXF-2973:
---------------------------------------
Other than the error check I put in earlier today, is there anything else we
should do about this?
We have a whole slew of declared dependencies on jaxb-impl. I had to exclude
them all to get rid of this problem.
I don't claim to understand how I ended up with the package-info referencing
the annotation from the webapp classloader, and the code in JAXB looking at the
annotation referencing the other. (or vica versa). It suggests that the
package-info was somehow touched in the 'outer' class loader while the JAXB
code didn't get hit until inside the webapp.
> Schema with broken namespaces in JAXB
> -------------------------------------
>
> Key: CXF-2973
> URL: https://issues.apache.org/jira/browse/CXF-2973
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.2.10
> Reporter: Benson Margulies
>
> Under some complex set of conditions that I have not yet diagnosed, the
> JAXBDataBinding will, with 'help' from JAXB (the version of JAXB built into
> the Apple 1.6 JDK, at least) create a schema DOM document that looks,
> roughly, like:
> {code}
> <schema xmlns:xs="......">
> <import .../>
> ...
> </schema>
> {code}
> That is, the elements are created with no namespace at all.
> I have not been able to isolate a test case, but I am opening this issue to
> track with.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
