It is very important and tricky to escape special characters whatever you are doing. In Siebel eScripts we do this escaping by using "\" . Same holds true while invoking any request from SOAP UI. Recently we hit an issue with one of our webservices as it was working fine for all accounts data but failed for couple of records.
While invoking the request from SOAP UI, we were getting response as "Supplied input in not well formed". Closer look of input exposed usage of '&' was giving the error. Yes you thought it right we need to escape special characters in request message.
Characters like "<",">","&" are criminals in XML.Once escaping is done the result was as expected. If you need to pass heavy duty XML message as request then the only gotcha is explicit CDATA sections where the special meaning doesn't hold.
So better Know Escaping else No Escaping.
While invoking the request from SOAP UI, we were getting response as "Supplied input in not well formed". Closer look of input exposed usage of '&' was giving the error. Yes you thought it right we need to escape special characters in request message.
Characters like "<",">","&" are criminals in XML.Once escaping is done the result was as expected. If you need to pass heavy duty XML message as request then the only gotcha is explicit CDATA sections where the special meaning doesn't hold.
So better Know Escaping else No Escaping.
