SOAP UI Return XML Dumping with Invalid Characters
Introduction: Hello Community! I hope I am posting in the correct place.
Precursory Information: I am currently using SOAP UI Free to attempt to validate a WSDL. I have a service that looks like this:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header> </SOAP-ENV:Header> <SOAP-ENV:Body> ...SOAP BODY HERE... </SOAP-ENV:Body> </SOAP-ENV:Envelope>
This sends out ok, and I get a return message.
Precursory Explination: The way my return code is designed is to send a response with an XML attached. I've done research on Request/Reponse with attachment's in SOAP UI, and it looks like it can do it. I've read the documentation on attachment's, and done additional research on SOAP UI but I cannot find my exact issue.
Issue: When returning the XML, I am recieving a bunch of invalid characters, along with a 'dump' of the attached xml. It looks like:
) ) [Invalid Character Here]uuid:XXXXXXX-YYYY-ZZZZ-AAAA-123456789123 <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body/></soapenv:Envelope> [Invalid Character Here]XXXXXXYYYYYYYYYZZZZZZZZZZ11111112222222233333333333/xml ...CORRECT XML THAT IS SUPPOSED TO BE ATTACHED HERE...
Note: I am not sure how much I am allowed to share of the code/digits - but the ...CORRECT... is a correct XML I am expecting, and the XYZA and 1234... are all characters that change every time.
Is there a way to prepare SOAP UI for this attached XML and not get this dump? I won't be able to validate this the way it is.
What I have tried: I have tried adjusting all of the settings in the Request Properties windows with no luck.
Has anyone experienced this? Could someone help me prepare my SOAP UI for the attached XML, rather than dump different characters and the contents?
Thanks in advance!
I wanted to follow up on this. After disregarding what I thought, and doing full testing in seperate applications - I found that nmrao was correct. This is how the response shows up in any program, and the code currently intercepts the message and pulls of the attachment.
Thank you community for your help!