You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2017/03/30 19:53:41 UTC
[jira] [Resolved] (CXF-3918) Java first with external XSD does not
resolve name spaces properly
[ https://issues.apache.org/jira/browse/CXF-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-3918.
------------------------------
Resolution: Fixed
Assignee: Daniel Kulp
Fix Version/s: 3.0
This seems to be working fine now with the latest releases. No idea when it was actually fixed.
> Java first with external XSD does not resolve name spaces properly
> ------------------------------------------------------------------
>
> Key: CXF-3918
> URL: https://issues.apache.org/jira/browse/CXF-3918
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.4.3
> Reporter: Kaj Kandler
> Assignee: Daniel Kulp
> Fix For: 3.0
>
> Attachments: CXF-WSDLTest.zip
>
>
> With CXF 2.4.3 working on Java first web services (attached Eclipse project CXF-WSDLTest.zip) produces the following error when attempting to generate WSDL with referenced XSD files.
> SEVERE: Schema element {urn:example.com:fault1}appFault references undefined type {urn:example.com:fault}appFaultDetails for service {urn:example.com:role1}RoleApiService.
> I want/need to do this, because several services do share the Fault, FaultDetails and error code beans.
> Here are my questions:
> * Why is java2ws not seeing the appFaultDetails (generating the severe message above)?
> * Why is java2ws not generating the import statement for the fault.xsd?
> * Why is the import statement for the role.xsd not using the stated location from the package-info.java file?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)