axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Martin" <>
Subject RE: [PROPOSAL] synchronizing character encoding between request and response
Date Tue, 02 Mar 2004 10:16:30 GMT
If I may weigh in, I don't agree with Simon's suggestion to use HTTP
headers. I believe that doing so would place (yet) another dependency on
using HTTP as the transport mechanism for SOAP messages. By implementing a
natural mirroring system as Ias suggests, character encoding issues become
much simpler for non-HTTP environments. 

I'm amazed that there isn't any mention of a mechanism in the WS-x
specifications to request a specific character encoding of the return



-----Original Message-----
From: Simon Fell [] 
Sent: 02 March 2004 06:01
Subject: Re: [PROPOSAL] synchronizing character encoding between request and

you misunderstand, the Accpet-Charset header indicates what charset
the client will accept for the response. It has nothing to do with the
content type of the request. This is a HTTP level thing that seems to
map exactly to what you are looking for, why re-invent the wheel ?


On Tue, 2 Mar 2004 13:59:30 +0900, in soap you wrote:

>> Wouldn't it be better for the server to use the 
>> Accept-Charset HTTP header ?
>This proposal is not an approach (for problems) about accepting character
>sets. What I'm intending is basically making a response XML message based
>the character encoding of its corresponding request XML message. If you
>the XML (SOAP) message over HTTP, it's no wonder that charset of
>Content-Type header and encoding of XML declaration in the message are the
>> Cheers
>> Simon
>> On Tue, 2 Mar 2004 12:17:26 +0900, in soap you wrote:
>> >Hi all,
>> >
>> >I'd like to propose simple changes to AxisServlet, Message and 
>> >SerializationContextImpl as the subject of this message says. Let me 
>> >introduce an example. Currently, Axis returns a SOAP message 
>> based on 
>> >UTF-8 character encoding unless you customize the default 
>> differently. 
>> >If you send a request message like
>> >
>> ><?xml encoding="utf-16"?>
>> >...
>> >
>> >to a service deployed to Axis, you can get
>> >
>> ><?xml encoding="utf-8"?>
>> >...
>> >
>> >as the response of the request.
>> >
>> >This mechanism is O.K. , even regarding WS-I BP 1.0 because 
>> there' no 
>> >requirement for "giving the same character encoding back" in 
>> the profile.
>> >However, it's obvious that users expect the character encoding of a 
>> >request will be naturally the same with that of its corresponding 
>> >response since the request results in the response.
>> >
>> >I hope this "synchronizing character encoding" will be the default 
>> >behavior of Axis based on SOAP including the character encoding 
>> >specified by the "Content-Type" HTTP header.
>> >
>> >At last, these changes passed "ant clean all-tests".
>> >
>> >Looking forward to your opinion and comment,
>> >
>> >Ias
>> >
>> >=========================================================
>> >Lee, Changshin (Korean name)
>> >Ias (International name)
>> >               Company Web Site:
>> >               Personal Web Site:
>> >---------------------------------------------------------
>> >JSR 201, 204, 222 and 224 Expert Group Member Apache Web Services 
>> >Project Member R&D Center Tmax Soft, Inc.
>> >=========================================================

View raw message