[
https://issues.apache.org/jira/browse/CXF-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554206
]
Benson Margulies commented on CXF-1220:
---------------------------------------
Unfortunately, I now realize that this is a JAXB issue.
The problem here is that the reference to currencyCodeContentType inside
AmountType should be a qualified reference to the schema containing
currencyCodeContentType. CXF just uses the RI for this.
I recommend that you package up a test case for https://jaxb.dev.java.net. If
it were me, I'd just make a tarball with the classes, and then run the RI
generator program against them to show that the xsd that comes out is incorrect.
The CXF team is not in a position to create code-arounds for JAXB problems,
unfortunately.
It might also be that you could make some intervention in the intermediate Java
source that you seem to be generating with an xsd-to-Java tool that would cause
the later Java-to-xsd to produce more useful results.
> Confused or dropped namespace in WSDL generated by java2wsdl function in the
> cxf-codegen-plugin
> ------------------------------------------------------------------------------------------------
>
> Key: CXF-1220
> URL: https://issues.apache.org/jira/browse/CXF-1220
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.0.2
> Reporter: Bruce Snyder
> Assignee: Benson Margulies
> Attachments: logisticx.zip
>
>
> When deploying a web service in CXF via ServiceMix and importing the WSDL
> into SoapUI, I am receiving the following error:
> when pointing SoapUI at the web service, i'm getting an error stating: An
> error occured [http://localhost:8192/order-service/?wsdl:0: error:
> src-resolve.a: Could not find type '[EMAIL
> PROTECTED]:un:unece:uncefact:data:draft:UnqualifiedDataTypesSchemaModule:2'.
> Do you mean to refer to the type named [EMAIL
> PROTECTED]://logisticx.com/orderService/ (in _3Fwsdl)?], see error log for
> details
> I may be incorrect, but there seems to be some confusion in namespaces or a
> dropped namespace in the java2wsdl function that might be causing this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
