Return-Path: Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 71887 invoked by uid 500); 24 Jun 2003 17:42:38 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 71871 invoked from network); 24 Jun 2003 17:42:38 -0000 Message-ID: From: "Laenzlinger, Christof" To: "'axis-user@ws.apache.org'" Subject: Character Encoding other than UTF-8 with SwA Date: Tue, 24 Jun 2003 19:42:40 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C33A78.02178C10" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C33A78.02178C10 Content-Type: text/plain; charset="iso-8859-1" We are using an Axis (Axis 1.1 final) client to send SOAP Messages with attachments. I was trying to find out how it might be possible to change the character encoding of the SOAP part to something other than UTF-8. By looking at the source code I found that the character-encoding in this case is hard-coded SerializationContextImpl.java and MimeUtils.java UTF-8 seems to be also hard coded in case of a SOAP Message without attachments (see Message.java). I was wondering that character encoding can not be configured in such a great and flexible toolkit as Axis is. Did I miss something important? I did not look yet into the server side implementation. Can Axis handle different character encoding as a server? Christof Laenzlinger ------_=_NextPart_001_01C33A78.02178C10 Content-Type: text/html; charset="iso-8859-1" Character Encoding other than UTF-8 with SwA

We are using an Axis (Axis 1.1 final) client to send SOAP Messages with attachments.
I was trying to find out how it might be possible to change the
character encoding of the SOAP part to something other than UTF-8.

By looking at the source code I found that the character-encoding in this case is
hard-coded SerializationContextImpl.java and MimeUtils.java

UTF-8 seems to be also hard coded in case of a SOAP Message without attachments
(see Message.java).

I was wondering that character encoding can not be configured in such a great and flexible
toolkit as Axis is. Did I miss something important?

I did not look yet into the server side implementation. Can Axis handle
different character encoding as a server?


Christof Laenzlinger

------_=_NextPart_001_01C33A78.02178C10--