PayloadValidatingInterceptor ignores schema list [SWS-176]

[gregturn]

deno vichas opened SWS-176 and commented

see http://forum.springframework.org/showthread.php?t=26685

when using more than one schema element for PayloadValidatingInterceptor it only uses the first in the list. in the example below if i send a request that needs to use the LocationService.xsd file i get "2007-08-24 10:56:28,015 WARN endpoint.interceptor.PayloadValidatingInterceptor - XML validation error on request: cvc-elt.1: Cannot find the declaration of element 'm:GetDistanceRequest'.: m:GetDistanceRequest' is a root element of the LocationService.xsd file.

<property name="schemas">
                     <list>
                                          <value>/WEB-INF/xsd/VehicleLookupService.xsd</value>
                                                                                                                                                                                                                          <value>/WEB-INF/xsd/LocationService.xsd</value>                    		
                     </list>
</property>

---

Affects: 1.0

Referenced from: commits ec66469

[gregturn]

Arjen Poutsma commented

I've tried to reproduce this, I even wrote some additional unit tests. See http://springframework.svn.sourceforge.net/svnroot/springframework/spring-ws/trunk/xml/src/test/java/org/springframework/xml/validation/AbstractValidatorFactoryTestCase.java, the testMultipleSchemasValidMessage method.

[gregturn]

Arjen Poutsma commented

Closing 1.0.1 issues.

[gregturn]

Petr Stuchlik commented

Hi. So I stumbled on this exact problem after almost 9 years. I managed to reproduce the issue - check out https://github.com/stuchl4n3k/sws-176

It seems, that when using a bit more complex schema (imports, includes, inheritance, ...) may trigger this one.

[gregturn]

Petr Stuchlik commented

If it helps I'm running Linux 64bit with JDK 1.8 64bit and building with Apache Maven 3.3.9.

[gregturn]

Petr Stuchlik commented

Also, as a workaround I'm now using an extra PayloadValidatingInterceptor bean for each WS XSD.

[gregturn]

Mihael commented

@petr stuchlick - Petr, what do you mean by "using an extra

PayloadValidatingInterceptor

bean for each WS XSD" ? I have tried to add a new

PayloadValidatingInterceptor

to the interceptors list, but I still get the behaviour you described in the bug description.

[gregturn]

Petr Stuchlik commented

@mihael Create an interceptor bean for each WS XSD/namespace - see a snippet from my ws-endpoint-definition.xml below:

    <!-- Web-services use a specific validating Interceptor for each namespace. -->
    <ws:interceptors>
        <ws:payloadRoot namespaceUri="http://example.com/ws/ws1">
            <ref bean="payloadValidatingInterceptor_ofWebService1"/>
        </ws:payloadRoot>
        <ws:payloadRoot namespaceUri="http://http://example.com/ws/ws2">
            <ref bean="payloadValidatingInterceptor_ofWebService2"/>
        </ws:payloadRoot>
    </ws:interceptors>

    <bean id="payloadValidatingInterceptor_ofWebService1"
          class="org.springframework.ws.soap.server.endpoint.interceptor.PayloadValidatingInterceptor">
        <property name="schemas">
            <list>
                <value>classpath*:xsd/WebService1.xsd</value>
            </list>
        </property>
        <property name="validateRequest" value="true"/>
        <property name="validateResponse" value="false"/>
    </bean>
    <bean id="payloadValidatingInterceptor_ofWebService2"
          class="org.springframework.ws.soap.server.endpoint.interceptor.PayloadValidatingInterceptor">
        <property name="schemas">
            <list>
                <value>classpath*:xsd/WebService2.xsd</value>
            </list>
        </property>
        <property name="validateRequest" value="true"/>
        <property name="validateResponse" value="false"/>
    </bean>