Discussion
Phalanx Consultancy Limited
GB
Last activity: 30 Jul 2015 9:32 EDT
SOAP Service returning error
I am new to SOAP integration and had been working with a SOAP service. I generated the WSDL and uploaded into SOAP UI for testing. When i run the WSDL by proving some parameters in SOAP UI, there is an error throwing during run time. The error is as follows.
<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:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>Couldn't parse SOAP request envelope</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
WSDL is
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:PegaRULES:SOAP:AWDPackage:LTSSI-Work-MsgCase-Scanning">
<soapenv:Header/>
<soapenv:Body>
<urn:CreateNewScannedMsg soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<InquiryDate xsi:type="xsd:date">?</InquiryDate>
<transactionRef xsi:type="xsd:string">?</transactionRef>
<caseIndexDocId xsi:type="xsd:string">?</caseIndexDocId>
<InquirerName xsi:type="xsd:string">?</InquirerName>
<InquirerID xsi:type="xsd:string">?</InquirerID>
<InquiryAmount xsi:type="xsd:decimal">?</InquiryAmount>
<awdObjectKey xsi:type="xsd:string">?</awdObjectKey>
<Currency xsi:type="xsd:string">?</Currency>
<casetype xsi:type="xsd:string">?</casetype>
</urn:CreateNewScannedMsg>
</soapenv:Body>
</soapenv:Envelope>
I am not sure how to debug this as the error code indicates
|
|
The SOAPMessage object could not be processed because of a processing error, not because of a problem with the message itself. |
I am using SOAP 1.1 specification and want to understand how can I debug the problem.
PEG
IN
It looks like you aren't sending the required request parameters in SOAP request. Pass the required parameters that have been used to built SOAP service.
Pegasystems Inc.
CA
You haven't modified the sample request generated by soapUI. Replace '?' with valid values based on the xsd type.
For example, in this line
<InquiryDate xsi:type="xsd:date">?</InquiryDate>
'?' is not a valid xsd:date type value
Similarly, in this
<InquiryAmount xsi:type="xsd:decimal">?</InquiryAmount>
'?' is not a valid xsd:decimal type value
Virtusa Corp.
US
If the below fields are not required then you can skip in soap ui and test
<InquiryDate xsi:type="xsd:date">?</InquiryDate>
<InquiryAmount xsi:type="xsd:decimal">?</InquiryAmount>