Eirik Bjorsnos created CXF-6717:
-----------------------------------
Summary: Live WSDL regression: Fails updating schemaLocation in
catalog-imported schema
Key: CXF-6717
URL: https://issues.apache.org/jira/browse/CXF-6717
Project: CXF
Issue Type: Bug
Affects Versions: 3.1.4, 3.1.3
Reporter: Eirik Bjorsnos
We noticed a regression live WSDL XSD import schemaLocation updates.
The problem reproduces in 3.1.4 and 3.1.3, but not in 3.1.2.
The scenario is as follows:
* We have a contract-first WSDL HelloService.wsdl
* HelloService.wsdl imports hello.xsd using a relative schemaLocation
* hello.xsd imports hello-types.xsd using a catalog name / uri schemaLocation
* hello-types.xsd imports hello-types-imported.xsd using a relative
schemaLocation
When we access http://localhost:8080/ws/hello?xsd=urn:xsd/hello-types.xsd, the
reference to hello-types-imported.xsd is not updated. As a result of this, the
WSDL is unreadable from an external client.
In 3.1.3, the hello-types.xsd is presented like this:
{code}
<xsd:import namespace="http://hello.respiro.kantega.org/ws/hello-types-1.0";
schemaLocation="../xsd/hello-types-imported.xsd"/>
{code}
In 3.1.2, hellotypes.xsd was presented like this:
{code}
<xsd:import namespace="http://hello.respiro.kantega.org/ws/hello-types-1.0";
schemaLocation="http://localhost:8080/ws/hello?xsd=../xsd/hello-types-imported.xsd"/>
{code}
Looking through the bug fixes for 3.1.3, I noticed CXF-6034. Could this
regression be caused by changes related to that issue?
I'll create a stand-alone reproducing Maven project for this and put it on
Github.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
