8 Replies Latest reply on Apr 14, 2015 5:16 PM by asoldano

Wildfly 8.2.0.Final schema validation problem

oguz_karakus Mar 20, 2015 4:37 AM

Hi all,

after migrating from 8.1 to 8.2, schema validation for web services does not work anymore.

In our web service class, we have the @SchemaValidation (com.sun.xml.ws.developer.SchemaValidation) annotation and in standalone.xml we got the configuration to trigger schema validation:

 <subsystem xmlns="urn:jboss:domain:webservices:1.2">
            <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
            <endpoint-config name="Standard-Endpoint-Config">
                <property name="schema-validation-enabled" value="true"/>
            </endpoint-config>
            <endpoint-config name="Recording-Endpoint-Config">
                <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
                    <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>
                </pre-handler-chain>
            </endpoint-config>
            <client-config name="Standard-Client-Config"/>
        </subsystem>
<subsystem xmlns="urn:jboss:domain:weld:2.0"/>

This combination works fine on 8.1 but not on 8.2. Is there something i am missing on the configuration?

Regards,

Oğuz

1. Re: Wildfly 8.2.0.Final schema validation problem

asoldano Mar 20, 2015 5:14 AM (in response to oguz_karakus)

com.sun.xml.ws.developer.SchemaValidation is not going to work, as it's a Metro RI annotation.
The schema-validation-enabled option in webservices subsystem configs should work, instead; be sure to put it in proper endpoint-config and/or client-config depending on where you actually need it.
Alternatively, you can use the @org.apache.cxf.annotations.SchemaValidation on endpoints (be sure to have a dependency set to org.apache.cxf module in that case, though).

As a reference, you can look at the testcases at jbossws - Revision 19582: /stack/cxf/tags/jbossws-cxf-5.0.0.Beta2/modules/testsuite/cxf-tests/src/test/java/org/jboss/te… (which have been run against WFLY 8.1, 8.2 and current master).
Actions
2. Re: Wildfly 8.2.0.Final schema validation problem

asoldano Mar 20, 2015 5:16 AM (in response to asoldano)

Doc at Advanced User Guide - JBoss Web Services - Project Documentation Editor
Actions
3. Re: Wildfly 8.2.0.Final schema validation problem

oguz_karakus Mar 20, 2015 8:57 AM (in response to asoldano)
Hi again,

i removed the annotation, since annotation and xml configuration are told to be alternating methods.
<property name="schema-validation-enabled" value="true"/>
This property is still true on my standalone.xml

When i try a web service request on 8.1, xml schema validation works fine. But if i switch the server to 8.2, there is no schema validation at all.

instead; be sure to put it in proper endpoint-config and/or client-config depending on where you actually need it.

I couldn't understand that part, i expect setting the property should effect all incoming soap requests.
Actions
4. Re: Wildfly 8.2.0.Final schema validation problem

asoldano Mar 20, 2015 9:56 AM (in response to oguz_karakus)
oğuz karakuş wrote:

Hi again,

i removed the annotation, since annotation and xml configuration are told to be alternating methods.

<property name="schema-validation-enabled" value="true"/>

This property is still true on my standalone.xml

Quite strange... any chance you can provide a simple reproducer?

instead; be sure to put it in proper endpoint-config and/or client-config depending on where you actually need it.

I couldn't understand that part, i expect setting the property should effect all incoming soap requests.

My point is that the Standard-Endpoint-Config configuration is set to *endpoints* (all those not having an explicit endpoint config), so you can expect incoming messages on the endpoints to be validated. Should the endpoint have an explicit configuration, the schema-validation-enabled property should be declared in that configuration. Same reasoning applies to client configs.
Actions
5. Re: Wildfly 8.2.0.Final schema validation problem

oguz_karakus Mar 23, 2015 10:24 AM (in response to asoldano)
Hi again,

i tried to create a small java project to reproduce the error, which you can find attached. You can use the soap ui project inside, to test it.

If you deploy the project to 8.1 and call the web service, and if you remove the input <arg0>?</arg0> element, you will get a validation error, since this element is required on the xsd. Something like
<faultstring>Unmarshalling Error: cvc-complex-type.2.4.b: The content of element 'ws:getStuff' is not complete. One of '{arg0}' is expected.</faultstring>

But when you deploy it to 8.2 and remove the element, you will not get any error.

SchemaValidation.rar 11.5 KB
Actions
6. Re: Wildfly 8.2.0.Final schema validation problem

asoldano Mar 24, 2015 11:14 AM (in response to oguz_karakus)

Thanks for the reproducer, I've filled in a bug: [JBWS-3894] Schema validation regression - JBoss Issue Tracker
Actions
7. Re: Wildfly 8.2.0.Final schema validation problem

rsearls Apr 14, 2015 2:26 PM (in response to oguz_karakus)

The RAR file is corrupt. It is not readable by JAR or unzip. Can you fix it and repost?
Actions
8. Re: Wildfly 8.2.0.Final schema validation problem

asoldano Apr 14, 2015 5:16 PM (in response to rsearls)
I'ts not corrupt, it's simply a RAR archive, to be unpacked using unrar if on Linux/Unix ;-). Attached you find a zip version.

schemavalidation.zip 16.5 KB
Actions

Go to original post