You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Toshiyuki Kimura <to...@apache.org> on 2004/03/02 05:17:49 UTC
Re: [PROPOSAL] synchronizing character encoding between request
+ 0.5 from me, at this time. :)
I think it's very effective that we provide the synchronizing
mechanism for character encodings. But, how do you think about
excepting UTF-8 and UTF-16, Ias ?
These two encodings should be accepted all of XML processors,
but others are optional. That is, some of encodings from Axis
clients might not understandable by Axis runtime on a server.
How do you plan to take care of this ?
--
Toshi <to...@apache.org>
-----Original Message-----
From: Davanum Srinivas [mailto:dims@yahoo.com]
Sent: Tuesday, March 02, 2004 12:21 PM
To: axis-dev@ws.apache.org
Subject: Re: [PROPOSAL] synchronizing character encoding between request
and response
+1 from me. Go for it.
-- dims
--- Ias <ia...@tmax.co.kr> 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: 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.
> =========================================================
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
RE: [PROPOSAL] synchronizing character encoding between request
Posted by Ias <ia...@tmax.co.kr>.
> + 0.5 from me, at this time. :)
>
> I think it's very effective that we provide the
> synchronizing mechanism for character encodings. But, how do
> you think about excepting UTF-8 and UTF-16, Ias ?
>
> These two encodings should be accepted all of XML
> processors, but others are optional. That is, some of
> encodings from Axis clients might not understandable by Axis
> runtime on a server.
> How do you plan to take care of this ?
This synchronization has nothing to do with understanding the character
encoding of a request message from a client. Supposing "x" is a character
encoding that a server doesn't understand, and a client sends
<?xml encoding="x" ?>
...
,then the server fails to process the message before it responds. In other
words, the server can't handle the request due to the "x" encoding no matter
whether it tries the synchronization or not.
By the way, we should recommend either UTF-8 (ideally equivalent to ASCII)
or UTF-16 (efficient to double bytes character systems such as Japanese and
Korean) to both client and server side for (more) interoperability based on
WS-I Basic Profile. I believe J2EE and .NET are true supporters of the
consensus.
Ias
>
> --
> Toshi <to...@apache.org>
>
> -----Original Message-----
> From: Davanum Srinivas [mailto:dims@yahoo.com]
> Sent: Tuesday, March 02, 2004 12:21 PM
> To: axis-dev@ws.apache.org
> Subject: Re: [PROPOSAL] synchronizing character encoding
> between request and response
>
> +1 from me. Go for it.
>
> -- dims
>
> --- Ias <ia...@tmax.co.kr> 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: 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.
> > =========================================================
> >
>
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>