[CXF-6034] Wrong schemaLocation if jax-ws-catalog is used

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.1
• Fix Version/s: 3.0.3, 2.7.14
• Component/s: Simple Frontend
• Estimated Complexity: Unknown
• Assignee: Daniel Kulp
• Reporter: Pavol Mederly
• Created: 02/Oct/14 10:00
• Updated: 16/Feb/15 16:09
• Resolved: 27/Oct/14 19:47

Description

When

• using a WSDL-first approach,
• defining endpoints so that your (not generated) WSDL is provided,
• using jax-ws-catalog

the WSDL given out to the client is sometimes incorrect.

Specifically, having entries in jax-ws-catalog like these

    <public publicId="http://test.com/main/schema" uri="../main/schema.xsd" />
    <system systemId="http://test.com/main/schema" uri="../main/schema.xsd" />

    <public publicId="http://test.com/auxiliary/schema" uri="../auxiliary/auxiliary.xsd" />
    <system systemId="http://test.com/auxiliary/schema" uri="../auxiliary/auxiliary.xsd" />

And having XSD imports in your types section of WSDL like these:

<xs:schema targetNamespace="http://test.com/main/customer-service" ...>
    <!-- this fails -->
    <xsd:import namespace="http://test.com/main/schema" schemaLocation="http://test.com/main/schema"/>
    <!-- this works -->
    <xsd:import namespace="http://test.com/auxiliary/schema" schemaLocation="http://test.com/auxiliary/schema"/>
</xs:schema>

The resulting WSDL is like this (showing only the relevant part):

<xs:schema targetNamespace="http://test.com/main/customer-service" ...>
    <!-- this fails -->
    <xsd:import namespace="http://test.com/main/schema" schemaLocation="http://test.com/main/schema"/>
    <!-- this works -->
    <xsd:import namespace="http://test.com/auxiliary/schema" schemaLocation="http://localhost:9090/CustomerServicePort?xsd=http://test.com/auxiliary/schema"/
</xs:schema>

(note the wrong schemaLocation attribute in the first import)

The problem occurs when the URI of the resource being imported is the same as (except for its last segment) the URI of the WSDL itself. In this case, *http://test.com/main/*schema vs. *http://test.com/main/*customer-service.

I was able to fix this preliminarily by disabling "optimization" used in WSDLGetUtils.findSchemaLocation, namely this code:

        if (docBase != null && imp.getReferencedSchema() != null) {
            try {
                String baseURI = URLDecoder.decode(UrlUtils.getStem(docBase), "utf-8");
                String importURI = URLDecoder.decode(imp.getReferencedSchema().getDocumentBaseURI(), "utf-8");
                if (importURI.contains(baseURI)) {
                    schemaLocationURI = importURI.substring(baseURI.length() + 1);
                }
            } catch (Exception e) {
                //ignore
            }

        }

However, I'm sure this is in fact a workaround; there should exist a cleaner solution.