[CXF-6013] Incorrect relative schemaLocation presentation in published WSDL

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7.12, 3.0.1
• Component/s: Simple Frontend
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Michał Jaros
• Created: 18/Sep/14 16:12
• Updated: 18/Sep/14 16:12

Description

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:

wsdl/contract.wsdl
xsd/camt.053.001.01.xsd

And in wsdl having an import

<xsd:import namespace="urn:iso:std:iso:20022:tech:xsd:camt.053.001.01" schemaLocation="./../xsd/camt.053.001.01.xsd" />

will result with publishing exactly the same import instead of expected

<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" />

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.