cancel
Showing results for 
Search instead for 
Did you mean: 

Parsing error in soap adapter, synchronous scenario

harish_babu5
Participant
0 Kudos

Hi guys


I am getting this error when I run an interface, ecc to soap synchronous:

SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The formatter threw an exception while trying to deserialize the message: Error in deserializing body of request message for operation xyz. End element xyz from namespace http://tempuri.org/ expected. Found text 1. Line 1, position 148.


This is the message in the payload


<?xml version="1.0" encoding="UTF-8"?>

<ns1:xyz xmlns:ns1="http://aaaaa.org/">1</ns1:ComplaintType>

Regards

Accepted Solutions (1)

Accepted Solutions (1)

engswee
Active Contributor
0 Kudos

Your start tag is xyz but end tag is ComplaintType. Both tags have to match. Whoever the sender of the payload is is sending an invalid XML.

harish_babu5
Participant
0 Kudos

Both types are complaintType only..

I am still getting the error

SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The formatter threw an exception while trying to deserialize the message: Error in deserializing body of request message for operation ComplaintType. End element ComplaintType from namespace http://tempuri.org/ expected. Found text 1. Line 1, position 148.


<?xml version="1.0" encoding="UTF-8"?>

<ns1:xyz xmlns:ns1="http://tempuri.org/">1</ns1:ComplaintType>

nitindeshpande
Active Contributor
0 Kudos

Hello Harish,

Can you try parsing your document using any browser? if there is any error then try to find out the same by using Notepad++.

The problem is here with missing or non-matching starting and ending tags.

Regards,

Nitin

PeterJonker
Active Contributor
0 Kudos

Check Eng Swee Yeoh's answer again.

Or give us the real xml, beacuse the one you show in your message have different start en end tags.

start = <ns1:xyz>

end = </ns1:ComplaintType>

Answers (0)