Posted: Thu Jun 29, 2017 6:20 am
Hard to say what the solution is here, or even what the "problem" is, without actually seeing what is actually "on the wire". Some things I would probably try:
a) what protocol are you using? REST? SOAP? ...does it happen with both?
b) test it with SOAPui, or if REST, a browser based plugin such as HTTP Requestor. Look at the "Raw" payload that is returned. Are the characters
escaped?
c) You note that it works when you write it to a file. What "kind" of file? Send the content in a test Job to an xmlOutput Stage. What do you get then? Look at the file in an editor...and then also look at the file using IE or a browser/tool that parses xml. See if the escapes get converted when open and processed by an xml-aware tool.
Ernie
a) what protocol are you using? REST? SOAP? ...does it happen with both?
b) test it with SOAPui, or if REST, a browser based plugin such as HTTP Requestor. Look at the "Raw" payload that is returned. Are the characters
escaped?
c) You note that it works when you write it to a file. What "kind" of file? Send the content in a test Job to an xmlOutput Stage. What do you get then? Look at the file in an editor...and then also look at the file using IE or a browser/tool that parses xml. See if the escapes get converted when open and processed by an xml-aware tool.
Ernie