-
1. Re: Wildfly 13, schema-validation-enabled=false doesn't work
jewellgm Jul 19, 2018 10:41 AM (in response to rchionna)1 of 1 people found this helpfulThe web services implementation changed between AS 7.1 and Wildfly 8.2. The method that you are trying to use is for the Metro RI, while Wildfly now utilizes CXF. Probably the easiest way to disable schema validation is to annotate your web services classes with @org.apache.cxf.annotations.SchemaValidation.
https://www.radcortez.com/wildfly-apache-cxf-and-schemavalidation/
-
2. Re: Wildfly 13, schema-validation-enabled=false doesn't work
rchionna Aug 16, 2018 9:55 AM (in response to jewellgm)Thank you Greg, finally I use the annotation in my web services to disable schema validation and all works fine
-
3. Re: Wildfly 13, schema-validation-enabled=false doesn't work
jewellgm Aug 17, 2018 8:26 AM (in response to rchionna)I just re-read the original post. I'm not sure whether it was edited, or whether I was just seeing something that wasn't there. The original way that you configured things should have worked, because that is the non-programmatic way to configure schema validation in wildfly. However, schema validation is disabled by default. Did you try simply removing that configuration for "Standard-Endpoint-Config" and "Standard-Client-Config"? I'm glad that you got things working with the annotations, but I don't know why your original configuration didn't work.
-
4. Re: Wildfly 13, schema-validation-enabled=false doesn't work
rchionna Aug 17, 2018 8:48 AM (in response to jewellgm)Hi Greg, the same configuration (standalone.xml) in JBoss AS 7.1 works fine, so my disappoint when I see a different behaviour in Wildfly (I use CXF in JBoss AS 7.1 too). I had tried several ways to bypass the problem, also removing "Standard-Endpoint-Config" from configuration file, but always unsuccesfully.
Once all worked fine via annotations, I didn't try more.
Thank you for your reply.
Have a nice day,
Roberto