Ok, I got an answer on this. Here is the scoop:
Any document, regardless wether it is XML or nonXML, which “smells” like an encoded text, will be converted by Tamino to it’s internal encoding format. When you get the document out of Tamino it will be encoded according the default encoding (a Tamino parameter), which is by default “iso-8859-1”, unless the “accept-charset” in the HTTP-header is specified. The Tamino API for Java sets the “accept-charset” to “UTF-8”, because the is the natural thing to do, if you want to convert it to Java Strings anyway. This is why you get it back in “UTF-8” and you have to use “UTF-8” to convert it e.g. to a String.
Is this a problem for you?
[This message was edited by Christian Gengenbach on 20 Dec 2002 at 10:46.]
#webMethods#API-Management#webMethods-Tamino-XML-Server-APIs