I am using SOAP sender scenarios on a process orchestration 7.4 with the latest SP. I have xsd validation activated in the iFlow. Now I remember that a long time ago (I think somewhere around PI 7.11) we got back meaningful XML parser errors in the response message from PI, so that a web service consumer could easily analyze what went wrong and correct the sent XML.
But since update to 7.3 (I think) all we get back in case of synchronous validation errors is:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Body> <SOAP:Fault> <faultcode>SOAP:Server</faultcode> <faultstring>Server Error</faultstring> <detail> <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0"> <context>XIAdapter</context> <code>ADAPTER.JAVA_EXCEPTION</code> <text>See log trace with id: n/a</text> </s:SystemError> </detail> </SOAP:Fault> </SOAP:Body> </SOAP:Envelope>
You can see the <text> information is absolute meaningless, not even pointing to a logID anymore.
So my question is: Is there a way to get back meaningful validation errors of the parser in the text field? It was like that before, so maybe there is a way to achieve this in customizing or with some hidden adapter module setting?