Jan 22nd, 2013, 09:58 AM
[solved] PayloadValidatingInterceptor doesn't validate unqualified attributes correct
my schema defines some attributes in the root element.
If I configure the schema to use unqualified attribute names, the PayloadValidatingInterceptor identify the incoming messages as invalid.
If I configure the schema to use qualified attributes, it works with the Interceptor.
I already implemented an own interceptor class and used the javax.xml-Implementation of the xml validator.
There is the same behaviour.
When I use the javax.xml-validator or the spring-validator outside the webservice in a unit test and validates the payload against the schema, everything is ok (either with qualified or unqualified attributes).
Why does the interceptor behaves different to a local implementation and "hates" my schema?
edit forgot to say:
Last edited by steyze; Jan 23rd, 2013 at 05:55 AM.
Tags for this Thread