Hi Harm
The files you attached work fine here too. (btw I've esb v.1.7.1).
The problem occurs with slightly different input.
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
<SOAP-ENV:Body>
....
The difference is that in the <issue/> there is no xsd namespace
definition.
I suspect this is still valid xml,
Yes - if you consider the whole message it is valid
and the validator _should_ accept this. Right ?
Let me explain what happens here.. we select the first child of the SOAP
envelope, or the result of the given XPath expression - which has
effectively removed the XSD namespace from the XPath result. This
probably happens in the Jaxen code, but we can define all namespaces in
the SOAP envelope to this result, to overcome this issue ..
Could you please raise a JIRA for this issue under Synapse, and we can
get it fixed
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
