Replies are sometimes using ISO-8859-1character set

Hello,
I am using iCloud - and iCloud Mail - in OSX 10.10.2 Yosemite on Macs (several different Macs).
Sometimes -- rarely -- when I do a reply to all and I look at the reply I mailed out under the "Sent" tab, I see that the whole reply is "garbled".
Loads of A's and 0's.
The actual reply is preceded with a text that resembles this (the numbers change from reply to reply):
Quote
--Apple-Webmail-42--c10907ed-7ae8-475d-80.....followed by more numbers
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=ISO-8859-1;
format=flowed
Unquote
The above "header" is followed by my reply that is completely garbled up too.
How can I avoid this formatting from happening?
Thanks in advance for your help.

LDAP is UTF-8 and Oracle is set to ISO-8859-1. Now
the problem is user info goes Oracle first and is
being validated by another UTF-8 based application
and then goes to LDAP. You are lucky things start in ISO-8859-1, because it encodes a proper subset of UTF-8. However, for characters beyond 127, UTF-8 encodes the character differently than ISO. Consequently, on the transition between Oracle and the UTF-8 based application, characters need to be recoded. Similarly, when characters come out of LDAP in UTF-8, they must be recoded to ISO if this is the encoding of your pages.
In this process all the
characters are getting distorted and I cannot change
LDAP and Oracle default charsets.Well, then there is no way around a recode. You cannot even try to trick the UTF-8 based application if it is slightly picky, because some ISO codes are simply illegal in UTF-8. The other way round would work: store UTF-8 in an ISO based application without recoding. At some point the ISO based application would just see two funny characters where there is only one, but as long as this does not distort any alphabetical sorting or even presentation to a user, you would just not care.
Harald.

Similar Messages

Export using ISO-8859-1 in XE Apex

Hello
I downloaded Oracle XE (the one with a lot of languages) and installed it in my pc.
When I try to export an application in Apex, the "File Character Set" says Unicode UTF-8.
Can you please tell me how to change it? I think we changed it sometime in a full version of Apex updating the character set to WE8ISO8859P1 in some file, but if that's the solution, could you tell me the name and location of the file in the XE version of Apex?
This information may help; i found it in Administration > About Database > National Language Support:
NLS_CHARACTERSET     AL32UTF8
NLS_NCHAR_CHARACTERSET     AL16UTF16
NLS_LANGUAGE     AMERICAN
I don't know if the problem is there, because I've used characeters like áéíóúñ in my applications titles and items and that worked fine; the problem appears when I try to export; when I import the application with another id, obviously those characters change because the export used UTF-8.
Thanks in advance

Hello,
I don't have much experience with the XE version, but I don't think there is a difference, regarding the export, between the versions. You can't change the export character set, and it will always reflect the DAD character set, which means that for versions 2.0 and above it will be utf-8.
I'm not sure your problem is with the export character set, but more with the target database character set, and the possible conversion between uft-8 and the local character set. Please read the following post, By Joel, and see if it can clear up your situation - Re: Application Express and NVARCHAR2 .
Hope this helps,
Arie.

Jaxb unmarshal error due to iso-8859-15 character set

I am currently attempting to use JAXB to handle XML unmarshaling. Is there a way to set the encoding used to unMarshall a message to iso-8859-15 as the messages coming in do not have an xml header with encoding specified?

I don't understand. If the XML messages coming in don't specify their own encoding, then their encoding must be UTF-8 or UTF-16. There's no possibility that their encoding can be ISO-8859-15. So why would you want to use ISO-8859-15 to decode them?

Put euro symbol in ISO-8859-1 database

is it possible to use jdbc to store a euro symbol in oracle with character set ISO-8859-1 then retrieve the information with jdbc and write it to a ISO-8859-15 textfile and display the euro symbol properly. i'm trying to do this and it doesn't work. as output i use a OutputStreamWriter object in Java using ISO-8859-15 to create an XML file and then i open it in Internet Explorer. it doen't recognize the euro symbols. strange thing is that when i view the source in notepad it does display the euro symbols properly. just using the OutputStreamWriter to write euro symbols also works well.
i'm trying to find out what is causing this problem but i'm not quite sure. i never before had problems with character sets so it's all a bit new to me.
thank you in advance.

The ISO-8859-1 character set does not contain the Euro character, so the database cannot hold it properly. If you want the Euro character to appear in your database, you would have to change the database character set to something that can store the euro character (or make use of your national character set, if that will store the euro character).
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

How to interface greek fonts (iso-8859-7) with labview for linux 8.5.1

I am trying to interface an Labview Linux application with greek fonts ,how i can achieve this out ? I want to use iso-8859-7 icharset. I am using a gentoo distro. Can anyone help me ?
thanks....
Ελευθερία σημαίνει ότι μαθαίνεις να έχεις απαιτήσεις μόνο από τον εαυτό σου, όχι από τη ζωή ή τους άλλους

Hi Sak1s,
Are you looking to create labels and captions with Greek fonts? You may be interested in the LabVIEW Help topic on Localizing VIs.
Jennifer R.
National Instruments
Applications Engineer

UTF-8 encoding vs ISO 8859-1 encoding

The iTunes tech specs call for UTF-8 encoding of the XML feed file; a friend of mine uses feed generator software through his blog that uses ISO 8859 encoding. Is there a way to convert the latter to UTF-8 so that iTunes tags may be successfully added?
When I tried editing his XML file, I got error messages when I submitted the file to RSS feed validator sites (such as http://feedvalidator.org/. Any help or knowledge is appreciated because I am not the least bit expert in this coding arena.

You don't need to convert iso 8859-1 (us-ascii) to utf-8 unless you have nonstandard characters. Basically, ascii is a subset of utf-8 and for English it will serve you just fine. You can have iTunes tags in the xml file even if the file itself is encoded in iso 8859-1.
The error you see at feedvalidator.org is most likely a warning.
Hope this helps!
- Andy Kim
Potion Factory
http://www.potionfactory.com

IE 9 incorrectly encoding Unicode characters in URIs to ISO-8859-1 instead of UTF8

Lets take the example word
präsentation
In Firefox, if I specify that as a CGI parameter, on the receiving end, I recieve:
pr\\303\\244sentation
which decoded as UTF-8 gives me: pr{U+00E4}sentation or my submitted word präsentation.
What does IE give me, well let's see.
pr\\344sentation
which well, doesn't decode as UTF8 because 0o344 is 0xE4.
ä in Unicode is at the codeopint 0xE4. Which as we've seen above, encoded to UTF8 is
0xC3 0xA4
So question boils down to this.
Why does IE9 use ISO-8859-1 instead of UTF8 for non-ASCII characters in URIs?

Hi,
As my understanding, you could choose the encoding ways by yourself:
Change your Internet Explorer 9 language
encoding settings
Alex Zhao
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Message.getSubject() with ISO-8859-1

Hello,
I'm trying to read the subject of a javax.mail.Message called message into a String:
String sTxtRequest=this.byteArrayToString(message.getSubject().getBytes("ISO-8859-1"));
public String byteArrayToString(byte[] bA)throws IOException{
String s=new String(bA, "ISO-8859-1");
return s;
Problem is, I never get german Umlaute (�, �, � etc) right.
I suppose that with calling message.getSubject() not ISO-8859-1 is used as a charset, but the platform's default character encoding. Is there any way to force the application to use ISO-8859-1 instead (without changing the default character encoding)?
Thank you,
rs

should be...
((MimeMessage)msg).setSubject(m_subject, "big5");
Message class has
abstract void setSubject(java.lang.String subject)
MimeMessage class has
void setSubject(java.lang.String subject, java.lang.String charset)

How to set the Xml Encoding ISO-8859-1 to Transformer or DOMSource

I have a xml string and it already contains an xml declaration with encoding="ISO-8859-1". (In my real product, since some of the element/attribute value contains a Spanish character, I need to use this encoding instead of UTF-8.) Also, in my program, I need to add more attributes or manipulate the xml string dynamically, so I create a DOM Document object for that. And, then, I use Transformer to convert this Document to a stream.
My problme is: Firstly, once converted through the Transformer, the xml encoding changed to default UTF-8, Secondly, I wanted to check whether the DOM Document created with the xml string maintains the Xml Encoding of ISO-8859-1 or not. So, I called Document.getXmlEncoding(), but it is throwing a runtime error - unknown method.
Is there any way I can maintain the original Xml Encoding of ISO-8859-1 when I use either the DOMSource or Transformer? I am using JDK1.5.0-12.
Following is my sample program you can use.
I would appreciate any help, because so far, I cannot find any answer to this using the JDK documentation at all.
Thanks,
Jin Kim
import java.io.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
public class XmlEncodingTest
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Transformer transformer = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Yes\" />\n")
                 .append("</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("initial xml = \n" + xmlStrBuf.toString());
        try
            //Test1: Use the transformer to ouput the xmlStrBuf.
            // This shows the xml encoding result from the transformer which will change to UTF-8
            tFactory = TransformerFactory.newInstance();
            transformer = tFactory.newTransformer();
            StreamSource ss = new StreamSource( new StringBufferInputStream( xmlStrBuf.toString()));
            System.out.println("Test1 result = ");
            transformer.transform( ss, new StreamResult(System.out));
            //Test2: Create a DOM document object for xmlStrBuf and manipulate it by adding an attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new StringBufferInputStream( xmlStrBuf.toString()));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document. the encoding becomes UTF-8
            DOMSource source = new DOMSource(document);
            StreamResult result = new StreamResult(System.out);
            System.out.println("\n\nTest2 result = ");
            transformer.transform(source, result);
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
    public static void main( String arg[])
        XmlEncodingTest xmlTest = new XmlEncodingTest();
        xmlTest.performTest();
}

Thanks DrClap for your answer. With your information, I rewrote the sample program as in the following, and it works well now as I intended! About the UTF-8 and Spanish charaters, I think you are right. It looks like there can be many factors involved on this subject though - for example, the real character sets used to create an xml document, and the xml encoding information declared will matter. The special character I had a trouble was u00F3, and somehow, I found out that Sax Parser or even Document Builder parser does not like this character when encoding is set to "UTF-8" in the Xml document. My sample program below may not be a perfect example, but if you replaces ISO-8859-1 with UTF-8, and not setting the encoding property to the transfermer, you may notice that the special character in my example is broken in Test1 and Test2. In my sample, I decided to use ByteArrayInputStream instead of StringBufferInpuptStream because the documentation says StringBufferInputStream may have a problem with converting characters into bytes.
Thanks again for your help!
Jin Kim
import java.io.*;
import java.util.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
* XML encoding test for Transformer
public class XmlEncodingTest2
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Resoluci�n\">\n")
                 .append("Special charatered attribute test")
                 .append("\n</ELEM>")
                 .append("\n</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("**** Initial xml = \n" + xmlStrBuf.toString());
        try
            //TransformerFactoryImpl transformerFactory = new TransformerFactoryImpl();
            //Test1: Use the transformer to ouput the xmlStrBuf.
            tFactory = TransformerFactory.newInstance();
            Transformer transformer = tFactory.newTransformer();
            byte xmlbytes[] = xmlStrBuf.toString().getBytes("ISO-8859-1");
            StreamSource streamSource = new StreamSource( new ByteArrayInputStream( xmlbytes ));
            ByteArrayOutputStream xmlBaos = new ByteArrayOutputStream();
            Properties transProperties = transformer.getOutputProperties();
            transProperties.list( System.out); // prints out current transformer properties
            System.out.println("**** setting the transformer's encoding property to ISO-8859-1.");
            transformer.setOutputProperty("encoding", "ISO-8859-1");
            transformer.transform( streamSource, new StreamResult( xmlBaos));
            System.out.println("**** Test1 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //Test2: Create a DOM document object for xmlStrBuf to add a new attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new ByteArrayInputStream( xmlbytes));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document.
            DOMSource source = new DOMSource(document);
            xmlBaos.reset();
            transformer.transform( source, new StreamResult( xmlBaos));
            System.out.println("\n\n****Test2 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //xmlBaos.flush();
            //xmlBaos.close();
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
        finally
    public static void main( String arg[])
        XmlEncodingTest2 xmlTest = new XmlEncodingTest2();
        xmlTest.performTest();
}

How to set codepage iso-8859-1 in output XML?

Dear experts,
I want to create an XML file with codepage "iso-8859-1" from PI 7.11.
I have already tried to put the filetype to TEXT and ISO-8859-1 in the File Encoding field of my receiving CC (using the FTP adapter), but I still get an xml in codepage UTF-8.
It should also be possible to realise this via an XSL mapping, but where do I have to do this? Or is there any other way to use codepage ISO-8859-1?
Thanks in advance,
William

Hi
You can do this change at Visual Administrator level. There are some parameters you need to edit and add IS0-8859, so that Integration engine will set for that encode.
So, you can ask the Basis guys to perform this.
This would certainly works out for you.
Regards
Pothana

Creating XML-files in ABAP with format ISO-8859-1 after the use of unicode

Hello,
We have a problem with XML-files created in z_abap-programma.
Before the use of unicode the XML-file was of the format: ISO-8859-1.
After the introducting of unicode the format is UTF-16.
In the abap-program we are using:
        CALL TRANSFORMATION xls-program
         SOURCE t_vbak = it_vbak
         RESULT XML xmlstring.
        CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
          EXPORTING
            text     = xmlstring
          IMPORTING
            buffer   = lx_xml_as_string.
        CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
          EXPORTING
            buffer        = lx_xml_as_string
          IMPORTING
            output_length = li_xml_size
          TABLES
            binary_tab    = ltb_xml_table.
        CALL METHOD cl_gui_frontend_services=>gui_download
          EXPORTING
            bin_filesize = li_xml_size
            filename     = lc_filename
            filetype     = 'BIN'
          CHANGING
            data_tab     = ltb_xml_table
          EXCEPTIONS
            OTHERS       = 24.
Is it prossible to create the XML-file with the format ISO-8859-1 after the unicode, please can you explane how to solve this problem.
Regards,
Theo Pijlman

hi theo,
did you read my thread i wrote some days before ? have a look in my sample coding find   " if_ixml_encoding ..... " there you can set the encoding of character .
greetz
tony
thread:
Re: abap to xml
SAP Explanation for Interface if_ixml_encoding :
http://help.sap.com/saphelp_nw04/helpdata/de/bb/5766a6dca511d4990b00508b6b8b11/content.htm

Use encode ISO-8859-7

Hi All,
     I'm new on this Forums and I want tell thanks to all for the help (I'm sorry if my english is not beatiful or correct)
     I'm using Flex on the last year and I have a web application for manage data arrive from file ASP.
     I need now to make a change on my application for read greek language. I set on my ASP the ISO for the language and all run well..
     But when I open a answer from ASP in Flex with mx:HTTPService the string on asp with greek symbol became in europe encode ISO-8859-1
     I try to change the setting of my pc to Greek but nothing change.
     Somebody know what is need to change for retrive this string in flex ?
     An other thing.. If I write in greek on a label in flex I saw the carachater without problem.
Please help me
Thank a lot for the helpand happy new year
Danny

b = GrammarText.getBytes(LastEncoding);
String strTemp = new String(b,EncodingType);Here you take a String (which is in Unicode) and convert it to bytes, using "LastEncoding". Next you take those bytes and convert them back to a String, assuming that they were encoded using "EncodingType". But they weren't, so at best this will do nothing and at worst it will produce garbage. It certainly won't do anything useful.
As I said all Java strings are in Unicode. If you want to convert something from one encoding to another encoding, you can only convert an array of bytes to a String using the first encoding, then convert that back to bytes using the second encoding. Converting a String to a String just makes no sense.

Character set conversion UTF-8 -- ISO-8859-1 generates question mark (?)

I'm trying to convert an XML-file in UTF-8 format to another file with character set ISO-8859-1.
My problem is that the ISO-8859-1 file generates a question mark (?) and puts it as a prefix in the file.
?<?xml version="1.0" encoding="UTF-8"?>
<ns0:messagetype xmlns:ns0="urn:olof">
<underkat>testv��rde</underkat>
</ns0:messagetype>
Is there a way to do the conversion without getting the question mark?
My code looks as follows:
public class ConvertEncoding {
     public static void main(String[] args) {
          String from = "UTF-8", to = "ISO-8859-1";
          String infile = "C:\\temp\\infile.xml", outfile = "C:\\temp\\outfile.xml";
          try {
               convert(infile, outfile, from, to);
          } catch (Exception e) {
               System.out.println(e.getMessage());
               System.exit(1);
     private static void convert(String infile, String outfile,
                                        String from, String to)
                         throws IOException, UnsupportedEncodingException
          //Set up byte streams
          InputStream in = null;
          OutputStream out = null;
          if(infile != null) {
               in = new FileInputStream(infile);
          if(outfile != null) {
               out = new FileOutputStream(outfile);
          //Set up character streams
          Reader r = new BufferedReader(new InputStreamReader(in, from));
          Writer w = new BufferedWriter(new OutputStreamWriter(out, to));
          /*Copy characters from input to output.
           * The InputSreamreader converts
           * from Unicode to the output encoding.
           * Characters that cannot be represented in
           * the output encoding are output as '?'
          char[] buffer = new char[4096];
          int len;
          while((len = r.read(buffer))!= -1) { //Read a block of output
               w.write(buffer, 0, len);
          r.close();
          w.flush();
          w.close();
}

Yes the next character is the '<'
The file that I read from is generated by an integration platform. I send a plain file to it (supposedly in UTF-8 encoding) and it returns another file (in between I call my java class that converts the characterset from UTF-8 to ISO-8859-1). The file that I get back contains the '��' if the conversion doesn't work and '?' if the conversion worked.
My solution so far is to skip the first "junk-characters" when reading from the inputstream. Something like:
private static final char UTF_BOM = '\uFEFF'; //UTF-BOM = ?
String from = "UTF-8", to = "ISO-8859-1";
if (from != null && from.toLowerCase().startsWith("utf-")) { //Are we reading an UTF encoded file?
/*Read first character of the UTF-Encoded file
It will return '?' in the first position if we are dealing with UTF encoding If ? is returned we skip this character in the read
try {
r.mark(1); //Only allow to read one char for the reset function to work
char c;
int i = r.read();
c = (char) i;
if (String.valueOf(UTF_BOM).equalsIgnoreCase(String.valueOf(c))) {
r.reset(); //reset to start position
r.skip(1); //Skip first character when reading from the stream
else {
r.reset();
} catch (IOException e) {
e.getMessage();
//return null;
}

Problem when setting encoding to ISO-8859-1

Hi. Is there something I'm missing when it comes to setting
encoding? Here are the code in the mxml:
<?xml version="1.0" encoding="ISO-8859-1"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
</Application>
In the html-template I'm setting:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1" />
The code for sending data from the app:
<mx:HTTPService
id="service"
url="encoding.jsp"
method="post"
showBusyCursor="true"
result="onResult(event)"
resultFormat="xml"
contentType="application/xml"
fault="onFault(event)"
useProxy="false" />
public function send():void {
var xml:XML = <Data>{data.text}</Data>;
service.send(xml);
But still the respons jsp I have made says it receives the
data in UTF-8 format? What am I doing wrong?
Servercode:
don't work: BufferedReader reader = new BufferedReader( new
InputStreamReader( is ) );
work: BufferedReader reader = new BufferedReader( new
InputStreamReader( is, "UTF-8") );

Are there no-one who have the same problem? I've tried
everything imaginable, and still the serverside receives the data
as UTF-8.
Is it supported at all to set the encoding of the
request?

Setting ISO-8859-1 Encoding in AXIS RPC call

As per my understanding UTF-8 is default for webservice call in AXIS implementation I may be wrong.
Is there any way to set ISO-8859-1 encoding in AXIS RPC call?
Below is the WSDL file details.
Thanks for you help.
Regards,
Hemen
<Code>
<?xml version="1.0" encoding="ISO-8859-1"?>
<definitions name="TestService_Service"
targetNamespace="http://webservice.de.rt.wsdl.WebContent/TestService_Service/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/"
xmlns:java="http://schemas.xmlsoap.org/wsdl/java/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://webservice.de.rt.wsdl.WebContent/TestService_Service/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<message name="getResponseRequest">
<part name="xml" type="xsd:string"/>
<part name="product" type="xsd:string"/>
<part name="source" type="xsd:string"/>
<part name="tran" type="xsd:string"/>
<part name="content" type="xsd:string"/>
</message>
<message name="getResponseResponse">
<part name="return" type="xsd:string"/>
</message>
<portType name="TestService">
<operation name="getResponse" parameterOrder="xml product source tran content">
<input message="tns:getResponseRequest" name="getResponseRequest"/>
<output message="tns:getResponseResponse" name="getResponseResponse"/>
</operation>
</portType>
<binding name="TestServiceJavaBinding" type="tns:TestService">
<java:binding/>
<format:typeMapping encoding="Java" style="Java">
<format:typeMap formatType="java.lang.String" typeName="xsd:string"/>
</format:typeMapping>
<operation name="getResponse">
<java:operation methodName="getResponse"
parameterOrder="xml product source tran content" returnPart="return"/>
<input name="getResponseRequest"/>
<output name="getResponseResponse"/>
</operation>
</binding>
<binding name="TestServiceBinding" type="tns:TestService">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getResponse">
<soap:operation soapAction="" style="rpc"/>
<input name="getResponseRequest">
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="distributionengine.com"
parts="xml product source tran content" use="encoded"/>
</input>
<output name="getResponseResponse">
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="distributionengine.com" use="encoded"/>
</output>
</operation>
</binding>
<service name="TestServiceService">
<port binding="tns:TestServiceJavaBinding" name="TestServiceJavaPort">
<java:address className="rt.de.webservice.TestService"/>
</port>
</service>
<service name="TestService_Service">
<port binding="tns:TestServiceBinding" name="TestServicePort">
<soap:address location="http://localhost:9080/servlet/rpcrouter"/>
</port>
</service>
</definitions>
</code>

try to put the below code at the top of the JSP page
<%@ page language="java" pageEncoding="UTF-8"%>

Replies are sometimes using ISO-8859-1character set

Similar Messages

Maybe you are looking for