-
Jan 22nd, 2013, 09:58 AM
#1
[solved] PayloadValidatingInterceptor doesn't validate unqualified attributes correct
Hi,
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).
So...
Why does the interceptor behaves different to a local implementation and "hates" my schema?
thx
edit forgot to say:
spring-ws-core-2.1.0.RELEASE
spring-xml-2.1.0.RELEASE
...
Last edited by steyze; Jan 23rd, 2013 at 05:55 AM.
-
Jan 23rd, 2013, 05:54 AM
#2
I solved it with the helpful answer in stackoverflow.
http://stackoverflow.com/questions/1...orrect-invalid
I had to transform the origin source to a String based StreamSource.
It seems the origin parser has a problem with the attributes.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules