axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anne Thomas Manes" <>
Subject RE: UTF-16 with Axis
Date Wed, 20 Nov 2002 13:54:46 GMT
Chinese and Japanese character sets are much more efficient in UTF-16 than
in UTF-8. So I can certainly understand why someone might want to use one
over the other.

Also, the WS-I Basic Profile [1] stipulates:

	R1012 MESSAGEs MAY be serialized as either UTF-8 or UTF-16.

In order to be conformant to the WS-I Basic Profile, a SOAP service (and the
SOAP implementation it uses) must support both UTF-8 and UTF-16. From the

	A deployed instance of a Web service (as specified by
      wsdl:port) is considered conformant if it produces only
      conformant artifacts, and is capable of consuming conformant
      artifacts, as appropriate. Note that this means that where
      multiple conformant artifacts are possible, a conformant
      service must be able to consume them all (e.g., while a
      sender may choose whether to encode XML in UTF-8 or UTF-16
      when sending a message, a receiver must be capable of using



> -----Original Message-----
> From: Yates, Danny (ANTS) []
> Sent: Wednesday, November 20, 2002 3:52 AM
> To: ''
> Subject: RE: UTF-16 with Axis
> Hi,
> SOAP messages are XML, and XML parsers are required (by the XML spec)
> to accept UTF-8 and UTF-16 encoding. Both encodings can represent
> exactly the same character set (Unicode). So, if AXIS is generating
> UTF-8, the recipient should have no difficulty parsing it (assuming
> it uses a conformant XML parser to do so), and you shouldn't be in
> a situation where you have to use UTF-16 because you can't represent
> certain characters in UTF-8.
> Perhaps you could be a bit more specific about why you require this?
> Regards,
> Dan.
> --
> Danny Yates
> Technical Architect
> Abbey National Treasury Services
> E-mail:
> Phone: +44 20 7756 5012
> Fax: +44 20 7612 4342
> -----Original Message-----
> From: Meng Cai []
> Sent: 19 November 2002 19:26
> To:
> Subject: UTF-16 with Axis
> Greeting,
> Does anyone know if Axis supports UTF-16? If so, how can I
> send a SOAP message with UTF-16 encoding?
> Thanks a lot,
> MC
> ******************************************************************
> *********
> This communication (including any attachments) contains
> confidential information.  If you are not the intended recipient
> and you have received this communication in error, you should
> destroy it without copying, disclosing or otherwise using its
> contents.  Please notify the sender immediately of the error.
> Internet communications are not necessarily secure and may be
> intercepted or changed after they are sent.  Abbey National
> Treasury Services plc does not accept liability for any loss you
> may suffer as a result of interception or any liability for such
> changes.  If you wish to confirm the origin or content of this
> communication, please contact the sender by using an alternative
> means of communication.
> This communication does not create or modify any contract and,
> unless otherwise stated, is not intended to be contractually binding.
> Abbey National Treasury Services plc. Registered Office:  Abbey
> National House, 2 Triton Square, Regents Place, London NW1 3AN.
> Registered in England under Company Registration Number: 2338548.
>  Regulated by the Financial Services Authority (FSA).
> ******************************************************************
> *********

View raw message