Forum Discussion
SmartBear_Suppo
16 years agoSmartBear Alumni (Retired)
Hi Michael,
great that you solved this! The initial problem was that a document only containing a CDATA section is not a valid XML document, which caused soapUI to wrap it in a "data" element. When adding the content-type header, soapUI "trusts" the response to be XML so it doesn't do any validation which renders the document as you want.. (but I still think it's an invalid XML document...)
regards!
/Ole
eviware.com
great that you solved this! The initial problem was that a document only containing a CDATA section is not a valid XML document, which caused soapUI to wrap it in a "data" element. When adding the content-type header, soapUI "trusts" the response to be XML so it doesn't do any validation which renders the document as you want.. (but I still think it's an invalid XML document...)
regards!
/Ole
eviware.com