axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Dean <Tony.D...@sas.com>
Subject RE: [Axis2] I18N problem
Date Thu, 03 Jul 2008 13:13:20 GMT
I will create a jira for this issue and assume that there are no workarounds for consumers
of Axis2 that are using Asian national language characters in their SOAP payload.

> -----Original Message-----
> From: Tony Dean
> Sent: Monday, June 30, 2008 6:49 PM
> To: axis-dev@ws.apache.org
> Subject: RE: [Axis2] I18N problem
>
> Sorry to say but the bug still exists with the new Axis2 1.4
> distribution using
> axis2-kernel-1.4.jar
> wstx-asl-3.2.4.jar
> axiom-api-1.2.7.jar
> axiom-dom-1.2.7.jar
> axiom-impl-1.2.7.jar
>
> Any other ideas?
>
> > -----Original Message-----
> > From: Tony Dean [mailto:Tony.Dean@sas.com]
> > Sent: Monday, June 30, 2008 2:09 PM
> > To: axis-dev@ws.apache.org
> > Subject: RE: [Axis2] I18N problem
> >
> > I will try the latest version to see if that makes a difference.
> > Thanks.
> >
> > > -----Original Message-----
> > > From: Andreas Veithen [mailto:andreas.veithen@skynet.be]
> > > Sent: Monday, June 30, 2008 12:33 PM
> > > To: axis-dev@ws.apache.org
> > > Subject: Re: [Axis2] I18N problem
> > >
> > > Tony,
> > >
> > > This should be handled by the StAX implementation. For Axis2 this
> is
> > > Woodstox by default. Maybe you can solve our problem by upgrading
> it
> > > to a newer version.
> > >
> > > Andreas
> > >
> > > On 30 juin 08, at 14:52, Tony Dean wrote:
> > >
> > > > Andreas,
> > > >
> > > > JVM is doing the right thing:
> > > >
> > > > getBytes("UTF-8") transforms \u4e2d \u6587 \u6d4b \u8bd5 into
> > > > [xe4 xb8 xad xe6 x96 x87 xe6 xb5 x8b xe8 xaf x95]
> > > >
> > > > I'm not sure where to look in the Axis2 code to determine what
> API
> > > > they are using to transform the payload to wire format.
> > > >
> > > > Thanks.
> > > >
> > > >> -----Original Message-----
> > > >> From: Andreas Veithen [mailto:andreas.veithen@skynet.be]
> > > >> Sent: Monday, June 30, 2008 6:24 AM
> > > >> To: axis-dev@ws.apache.org
> > > >> Subject: Re: [Axis2] I18N problem
> > > >>
> > > >> Tony,
> > > >>
> > > >> It would be interesting to know if it is a problem with Axis2 or
> > > with
> > > >> the UTF-8 implementation of the Java runtime environment. Can
> you
> > > >> test
> > > >> that by calling getBytes("UTF-8") on the string and check
> whether
> > > the
> > > >> result is correct?
> > > >>
> > > >> Andreas
> > > >>
> > > >> On 29 juin 08, at 08:19, Tony Dean wrote:
> > > >>
> > > >>> Hi,
> > > >>>
> > > >>> I have narrowed down an I18N problem when using Simplified
> > Chinese
> > > >>> characters in payload to Axis2 client side.
> > > >>>
> > > >>> I have an Axis2 client using ServiceClient to send a SOAP
> request
> > > to
> > > >>> my service.  For example a couple of characters in the payload
> > are
> > > >>> as follows:
> > > >>>
> > > >>> U+4e2d U+6587  U+6d4b U+8bd5
> > > >>>
> > > >>> When the service receives these characters, they appear as
> > follows:
> > > >>>
> > > >>> U+002d U+6587 U+004b U+8bd5
> > > >>>
> > > >>> The high-order byte of the 1st and 3rd characters are
> incorrect.
> > > >>>
> > > >>> When the Axis2 ServiceClient converts the payload to UTF-8 for
> > > >>> sending across the wire, these bytes become (as seen in
> > > >>> soapMonitor):
> > > >>> 2de6 9687 4be8 af95
> > > >>>
> > > >>> I think that they should be:
> > > >>> e4b8 ade6 9687 e6b5 8be8 af95
> > > >>>
> > > >>> Can anyone explain what's going on?  Seems like an easy
> > > >>> transformation of encodings for wire-format, but something is
> not
> > > >>> quite right.
> > > >>>
> > > >>> To replicate try the following:
> > > >>>
> > > >>>       ServiceClient client = new ServiceClient(ctx, null);
> > > >>>                    ...
> > > >>>
> > > >>>       String value = new String("Hello world:
> \u4e2d\u6587\u6d4b
> > > >>> \u8bd5");
> > > >>>       OMElement response =
> client.sendReceive(getPayload(value));
> > > >>>
> > > >>> The Asian characters are not sent as expected.
> > > >>>
> > > >>> Thanks for any insight.
> > > >>>
> > > >>> I'll enter a bug if it so warrants.
> > > >>>
> > > >>>
> > > >>>
> > > >>> Tony Dean
> > > >>> SAS Institute Inc.
> > > >>> 919.531.6704
> > > >>> tony.dean@sas.com
> > > >>>
> > > >>> SAS... The Power to Know
> > > >>> http://www.sas.com
> > > >>>
> > > >>>
> > > >>>
> > > >>> ---------------------------------------------------------------
> --
> > --
> > > --
> > > >>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > >>> For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >>>
> > > >>
> > > >>
> > > >> ----------------------------------------------------------------
> --
> > --
> > > -
> > > >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >>
> > > >
> > > >
> > > > -----------------------------------------------------------------
> --
> > --
> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >
> > >
> > >
> > > -------------------------------------------------------------------
> --
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message