[
https://issues.apache.org/jira/browse/CXF-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825817#comment-16825817
]
Andreas Rusch commented on CXF-8030:
------------------------------------
See [^cxf_WSDLToJavaContainer.patch] for my solution on how to replace the
included XSD locations.
Note that I needed to change the logic how the key for the hash map is created,
as the namespace is not unique in the case of includes.
> CXF WSDLToJava generated local WSDL does not map included local XSDs
> --------------------------------------------------------------------
>
> Key: CXF-8030
> URL: https://issues.apache.org/jira/browse/CXF-8030
> Project: CXF
> Issue Type: Bug
> Affects Versions: 3.3.1
> Reporter: Andreas Rusch
> Priority: Major
> Attachments: cxf_WSDLToJavaContainer.patch
>
>
> When generating a WS client with WSDLToJava from a WSDL with an included
> (instead of imported) XSD, the WSDL file that gets generated does not link to
> the locally downloaded XSD.
> The code properly downloads the included XSD and also replaces all import
> locations with the downloaded ones, but not for any XSDs that are included.
> After some debugging and I found out that the code for replacing the included
> locations (<xs:include schemaLocation="\{link_to_xsd}"/>) in
> WSDLToJavaContainer.generateLocalWSDL(ToolContext) is completely missing.
> This would mean that the XSD would be loaded from the web location during
> runtime.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
