Hi Harm
However using nusoap php as client code we found that the validator is
rejecting some type of perfectly valid messages.
It seems the validation mediator strips one namespace to many from the
message when passing the body into the validator.
.....
*Error in ESB logs*
DEBUG ValidateMediator Validation of element returned by XPath
:s11:Body/child::*[position()=1] | s12:Body/child::*[position()=1] failed
against the given schema(s) [rfid_xsd]with error : cvc-attribute.3: The value
'xsd:string' of attribute 'xsi:type' on element 'nu2702:accessStart'
is not valid with respect to its type, 'QName'. Executing 'on-fail' sequence
The validator itself seems to be right... it doesn't know the *xsd
*namespace (see message "xsd:string") so it gives an error.
The xsd namespace was in the original message, but got stripped by the
ESB before passing into the actual validator library.
Adding xmlns:xsd="http://www.w3.org/2001/XMLSchema"; to the validator
configuraion (synapse.xml) didn't work.
Any idea how to fix this problem?
Can you share the XSD and the synapse.xml to investigate into this issue?
We really like the idea of a validation step on the ESB inputs, but
rejecting valid messages, kind of beats the purpose :)
Sure, but lets understand what went wrong.. :)
cheers
asankha
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
_______________________________________________
Esb-java-user mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
