Validation on 7.31 AAE HTTP adapter does not deliver detailed error

Dear all,

I am working with a synchronous HTTP <-> PI <-> RFC on PI 7.31.

In the scenario I am using the validation by adapter option.

When I am using the HTTP adapter and classic configuration, in case of invalid payload being sent I am receiving back a clear error from the parser:

<?xmlversion="1.0"encoding="UTF-8"standalone="no"?>
- <Error>
- <Details>
- <![CDATA[
<SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>XML_VALIDATION_INB.CX_XMS_SYSERR_VALIDATION</SAP:Code><SAP:P1>com.sap.aii.utilxi.xmlvalidation.impl.XMLValidationException: XML Validation for payload with root element name message_root , target namespace http://www.root.net Failed!Errors Encountered During Parsing
1.cvc-enumeration-valid: Value 'fufu' is not facet-valid with respect to enumeration '[TECL, STRD]'. It must be a value from the enumeration.
2.cvc-type.3.1.3: The value 'fufu' of element 'RapidPriority' is not valid.
</SAP:P1><SAP:P2>XML Validation for payload with root element name message_root , target namespace http://www.root.net Failed!Errors Encountered During Parsing
1.cvc-enumeration-valid: Value 'fufu' is not facet-valid with respect to enumeration '[TECL, STRD]'. It must be a value from the enumeration.
2.cvc-type.3.1.3: The value 'fufu' of element 'RapidPriority' is not valid.
</SAP:P2><SAP:P3>Schema Not Available in Cache, try to validation with file system schemas. Validation With File System schemas also Failed. XML Validation for payload with root element name message_root , target namespace http://www.root.net Failed!Errors Encountered During Parsing
1.cvc-enumeration-valid: Value 'fufu' is not facet-valid with respect to enumeration '[TECL, STRD]'. It must be a value from the enumeration.
2.cvc-type.3.1.3: The value 'fufu' of element 'RapidPriority' is not valid.
</SAP:P3><SAP:AdditionalText>not used at the moment.</SAP:AdditionalText><SAP:Stack>System error occurred during XML validation</SAP:Stack></SAP:Error>
]]>
</Details>
</Error>

After changing the scenario to integrated configuration using the HTTP AAE adapter, I am receiving a response to the same error in such a way:

<?xmlversion="1.0"encoding="UTF-8"standalone="no"?>
- <Error>
- <Details>
- <![CDATA[
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Error Report</title>
<style>
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
A:link {color : #0059AA;}
A:visited {color : #999999;}
A:active {color : #999999;}
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
<tr bgcolor="#FFFFFF">
<td align="left" colspan="2" height="48"> 500 Internal Server Error</td>
</tr>
<tr bgcolor="#3F73A3">
<td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
<td height="23"><img width=1 height=1 border=0 alt=""></td>
<td align="right" height="23">SAP NetWeaver Application Server </td>
</tr>
<tr bgcolor="#9DCDFD">
<td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
</tr>
</table>
Error: ERROR_IN_MODULECHAIN;ERROR_IN_MODULECHAIN, senderChannel '2da99c2347883de1901ec9bd42dbf208': Catching exception calling messaging system
<a href="https://wiki.sdn.sap.com/wiki/x/wIN3Cw">SAP Technology Troubleshooting Guide</a>
<table>
<tr>
<td valign="top"> Details:</td>
<td valign="top"><PRE>No details available.</PRE></td>
</tr>
</table>
</body>
</html>
]]>
</Details>
</Error>