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
ISD Service Response not able to convert Extended characters
Ernie Ostic
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
Re: ISD Service Response not able to convert Extended charac
Can you provide more input as in What is the o/p format? and What is the NLS setting you are using?
Also try setting NLS_LANG=AMERICAN_AMERICA.UTF8, and see if it resolves your problem.
Also try setting NLS_LANG=AMERICAN_AMERICA.UTF8, and see if it resolves your problem.
- Neelabh Barve
- We aspire! Universe Conspires!!
- We aspire! Universe Conspires!!