[
https://issues.apache.org/jira/browse/CXF-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved CXF-6013.
--------------------------------------
Resolution: Fixed
Seems to be fixed now
> Incorrect relative schemaLocation presentation in published WSDL
> ----------------------------------------------------------------
>
> Key: CXF-6013
> URL: https://issues.apache.org/jira/browse/CXF-6013
> Project: CXF
> Issue Type: Bug
> Components: Simple Frontend
> Affects Versions: 2.7.12, 3.0.1
> Reporter: Michał Jaros
> Priority: Major
>
> When publishing WSDL witch contains relative schema imports, namely
> ./../schema.xsd with CXF Servlet the schemaLocation attributes won't get
> updated.
> For example having following file structure in project:
> {noformat}
> wsdl/contract.wsdl
> xsd/camt.053.001.01.xsd
> {noformat}
> And in wsdl having an import
> {code:xml}
> <xsd:import namespace="urn:iso:std:iso:20022:tech:xsd:camt.053.001.01"
> schemaLocation="./../xsd/camt.053.001.01.xsd" />
> {code}
> will result with publishing exactly the same import instead of expected
> {code:xml}
> <xsd:import namespace="urn:iso:std:iso:20022:tech:xsd:camt.053.001.01"
> schemaLocation="http://server/service?xsd=./../xsd/camt.053.001.01.xsd"; />
> {code}
> This is probably due to the code of method WSDLGetUtils.mapUri
> the specified code could have been introduced to fix the issue CXF-4910.
> In our project we had to specify schema location as ./../schema.xsd because
> such ../schema.xsd version wasn't correctly handled by NetBeans 6.8 wsdl
> import.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
