You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2019/04/26 10:44:00 UTC

[jira] [Assigned] (CXF-8030) CXF WSDLToJava generated local WSDL does not map included local XSDs

     [ https://issues.apache.org/jira/browse/CXF-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh reassigned CXF-8030:
----------------------------------------

    Assignee: Colm O hEigeartaigh

> 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
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>         Attachments: cxf_WSDLToJavaContainer.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)