[
https://issues.apache.org/jira/browse/CXF-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies resolved CXF-2973.
-----------------------------------
Fix Version/s: 2.2.11
Resolution: Fixed
'FIxed' is perhaps a strong statement, but ...
This problem was somehow caused by putting CXF into both the system classloader
of Jetty and also into a webapp class loader. One might argue that this is
supposed to work. On the other hand, it usually *does* work, and the failure
seems to be a JAX-B failure, not a CXF failure. Further, it may result from a
fundamental limitation of Java.
So, i'm resolving based on the submitted change that will at least diagnose
this a bit earlier and slightly less confusingly.
> 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
> Fix For: 2.2.11
>
>
> 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.
