SOA 11g: XSD Validation Detail Error Messages are not Returned to Caller when Validation is on in Mediator
(Doc ID 1537945.1)
Last updated on MARCH 29, 2019
Applies to:Oracle SOA Suite - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Have set the 'Validation Syntax(XSD)' property to true in a Mediator component. When the composite is run and the XSD schema validation fails, the XSD Validation Detail Error Message is not included in the fault details of the Response Message.
The following error is displayed. Note that it does not include the fault details.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received
SOAP Fault from server : null
Additional Trace Information:
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : null at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:808)
oracle.tip.mediator.infra.exception.MediatorException: ORAMED-01303:[Payload default schema validation error]XSD schema validation fails with error "Invalid text 'x12345' in element: 'rootOrderLineId'". Possible Fix:Fix payload and resubmit.
If the XSD schema validation fails, the requirement is for the XSD Validation Detail Error Message to be included in the fault in the response from the Mediator.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document