[
https://issues.apache.org/jira/browse/CXF-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552091
]
Benson Margulies commented on CXF-1220:
---------------------------------------
I think we fixed this a long time ago, but I'm not entirely certain.
One problem here is missing schema imports. In 2.0.2, we didn't generate the
required imports for inline schemas.
That having been said, I'm concerned that the schema using
currencyCodeImportType doesn't assign a namespace prefix and use it for the
reference.
I wish I could repro your issue (with the missing jar) ... I'm loath to do the
work of mocking up a test case if we've already fixed the problem.
Could you also outline the complete lifecycle? It seems as if some things are
travelling from XSD to Java to XSD? Obviously, currencyCodeContentType is of
particular interest.
> 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.
