Forum Discussion

kiwi7's avatar
kiwi7
New Contributor
4 years ago
Solved

Error in building a soaprequest

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 se...
  • kiwi7's avatar
    kiwi7
    4 years ago

    Thanks 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's avatar
HimanshuTayal
Community Hero
4 years ago

kiwi7 :

 

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.

 

Hope it will help you to resolve the issue. 🙂

  • kiwi7's avatar
    kiwi7
    New Contributor
    4 years ago

    Thanks 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.

    • richie's avatar
      richie
      Community Hero
      4 years ago
      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(&), quote('), doublequote("), less than (<) and greater than (>)

      Ta

      Rich