Error in building a soaprequest

Question

There seems to be a bug in composing a soap request when text in the body containing certain characters. On a request we got back that the message was not wellformed. Looking at the raw request we see a kind of mixing up with two body elements. Deducing we found out it goes wrong when the text contains the following characters "{${".&nbsp;When we have a request like this in the xml-view:&nbsp;&lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:oob="http://www.OOBCWS03.OOBI0103.Request.com"&gt;&nbsp;&nbsp; &lt;soapenv:Header/&gt;&nbsp;&nbsp; &lt;soapenv:Body&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:OOBCWS03Operation&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:OOBCWS03Operatie&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:cgn_tekstuit_indi&gt;xxx&lt;/oob:cgn_tekstuit_indi&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:tekstuiti&gt;{${&lt;/oob:tekstuiti&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/oob:OOBCWS03Operatie&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/oob:OOBCWS03Operation&gt;&nbsp;&nbsp; &lt;/soapenv:Body&gt;&lt;/soapenv:Envelope&gt;&nbsp;We see after the invoke in the raw-view, a kind of mixed up request:&nbsp;&lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:oob="http://www.OOBCWS03.OOBI0103.Request.com"&gt;&nbsp;&nbsp; &lt;soapenv:Header/&gt;&nbsp;&nbsp; &lt;soapenv:Body&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:OOBCWS03Operation&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:OOBCWS03Operatie&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:cgn_tekstuit_indi&gt;xxx&lt;/oob:cgn_tekstuit_indi&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:tekstuiti&gt;{&lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:oob="http://www.OOBCWS03.OOBI0103.Request.com"&gt;&nbsp;&nbsp; &lt;soapenv:Header/&gt;&nbsp;&nbsp; &lt;soapenv:Body&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:OOBCWS03Operation&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:OOBCWS03Operatie&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:cgn_tekstuit_indi&gt;xxx&lt;/oob:cgn_tekstuit_indi&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:tekstuiti&gt;{${&lt;/oob:tekstuiti&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/oob:OOBCWS03Operatie&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/oob:OOBCWS03Operation&gt;&nbsp;&nbsp; &lt;/soapenv:Body&gt;&lt;/soapenv:Envelope&nbsp;As far as we know the characters {$ don't have a special meaning in XML, so it shouldn.t be a problem.When we have a message with only "{$" (instead of "{${" ) the composing goes well:&nbsp;&lt;soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:oob="http://www.OOBCWS03.OOBI0103.Request.com"&gt;&nbsp;&nbsp; &lt;soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"&gt;&lt;wsa:Action&gt;http://www.OOBCWS03.OOBI0103.com/OOBCWS03Port/OOBCWS03OperationRequest&lt;/wsa:Action&gt;&lt;wsa:MessageID&gt;uuid:25baf000-fc16-4fb5-902a-bcad09970de9&lt;/wsa:MessageID&gt;&lt;wsa:To&gt;https://APMVST1.BELASTINGDIENST.NL:3304/OOBCWS03&lt;/wsa:To&gt;&lt;/soapenv:Header&gt;&nbsp;&nbsp; &lt;soapenv:Body&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:OOBCWS03Operation&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:OOBCWS03Operatie&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:cgn_tekstuit_indi&gt;xxx&lt;/oob:cgn_tekstuit_indi&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;oob:tekstuiti&gt;{$&lt;/oob:tekstuiti&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/oob:OOBCWS03Operatie&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/oob:OOBCWS03Operation&gt;&nbsp;&nbsp; &lt;/soapenv:Body&gt;&lt;/soapenv:Envelope&gt;&nbsp;The soapUI version we are using is 5.4.0. Are we doing something wrong or is this a bug?Kind regards,Iwan Mensink

kiwi7 · Accepted Answer

Thanks&nbsp;HimanshuTayal for your quick respons,Using /$ didn't help but you put me in right direction of escape characters, using $$ did the trick for me.Thanks again.

himanshutayal · Answer

kiwi7&nbsp;:
&nbsp;
Yes you are correct, character $ doesn't have any special meaning to XML but character $ have special meaning in soapui. You can use \ to escape the character.
&nbsp;
Hope it will help you to resolve the issue. 🙂

richie · Answer

Hey@kiwi7,Sorry ive only just seen your post.  Yeah the reason you was getting the error was cos soapui recognised the $ symbol as though you were using properties.  Adding an extra $ symbol, so it reads $$ indicates to soapui that it isnt a property placeholder.Dunno why the xmlparser was reporting the error as malformed xml though, as $ characters in tag values is allowed.  Actually dollar symbols in tagnames is allowed too....you just need to escape any of the 5 xml entities....ampersand(&amp;), quote('), doublequote("), less than (&lt;) and greater than (&gt;)TaRich

Forum Discussion

Error in building a soaprequest

3 Replies

Related Content

Object Properties Error - On a New Build

Run TestComplete tests into tfs builds Error

Maven build fails

Maven Build Error - Failed to execute goal com.smartbear:ready-api-maven-plugin:2.6.0

Property Transfer failed when run through maven maven build

Recent Discussions

clone TestSuite fails when there are more project with the same name

Will SOAP UI 5.6.1 work with JDK 8

SOAP Request works in SoapUI, but not in C# code

How to configure Swagger in Paas to use it in Oracle APEX instance.

log4j1.x vulnerability