RE: [PROPOSAL] synchronizing character encoding between request a nd response

[Tom Jordahl <to...@macromedia.com>]

+1

This seems to agree with the "principal of least surprise".
-1 to using the HTTP header - this is a XML level thing.

--
Tom Jordahl


-----Original Message-----
From: Ias [mailto:iasandcb@tmax.co.kr] 
Sent: Monday, March 01, 2004 10:17 PM
To: axis-dev@ws.apache.org
Subject: [PROPOSAL] synchronizing character encoding between request and
response

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: http://www.tmax.co.kr
               Personal Web Site: http://www.iasandcb.pe.kr
---------------------------------------------------------
JSR 201, 204, 222 and 224 Expert Group Member
Apache Web Services Project Member
R&D Center
Tmax Soft, Inc.
=========================================================