Thank you very much! The ${="\r"} - helps me a lot!
I have mocked response, and it is like yours, I mean my response also contains boundaries.
My problem was that SoapUI saves mock xml file, and as a break-line it uses "\n" (LF), at least in Windows 10, but I need normal windows "\r\n" (my response is consuming by some another service, and this service is looking for "\r\n", bot not for only "\n").
So, I go to SoapUI [Preferences] - [UI Settings] and checked there "Normalize line-break". After that Soap UI began using "\r\n" (CR LF) as a line-break.
But it did not solve my problem, because my Soap UI mock service (which was deployed to the Tomcat server) continued to reply me the xml with ONLY "\n".
And only when I added ${="\r\n"} - it started reply with correct line-break (that is precedes "\n")! I don't know whether it is a bug or just some magic, but I spent three days trying to solve it. And I would like to wish nobody will face this problem, or if they will, they can find my message.
P.S. I checked line-breaks with the help of Notepad++ ([View] - [Show Symbol] check Show All Characters)
