Why? Where in the spec does it say that? The client is (in the first instance) nothing more than an XML parser, which must understand both.
-- Danny Yates Technical Architect Abbey National Treasury Services E-mail: [EMAIL PROTECTED] Phone: +44 20 7756 5012 Fax: +44 20 7612 4342 -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] Sent: 20 November 2002 16:14 To: [EMAIL PROTECTED] Subject: RE: UTF-16 with Axis If a client sends you a request in UTF-16, you ought to send the response back in UTF-16. > -----Original Message----- > From: Yates, Danny (ANTS) [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 20, 2002 10:11 AM > To: '[EMAIL PROTECTED]' > Subject: RE: UTF-16 with Axis > > > Anne wrote: > > 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 > > profile: > > Ummm... not quite. Surely this means that a serialiser has to support > one or other (or both) of UTF-8 and UTF-16, but it cannot support > neither. If this is the case, all de-serialisers (i.e. XML parsers) > MUST be able to support either since they can never be sure which > they will receive. This is no different from the XML spec which states > that parsers must be able to understand both UTF-8 and UTF-16. So we > are no further forward. > > > 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 > > either). > > Err... yeah! That's what I said! :-) > > So (other than the efficiency issues you touched upon regarding > Chinese/Japanese characters), there is no reason to prefer one type > of output over another, as far as I can make out. > > We still need to know what the original poster was trying to achieve. > > Dan. > > -- > Danny Yates > Technical Architect > Abbey National Treasury Services > E-mail: [EMAIL PROTECTED] > Phone: +44 20 7756 5012 > Fax: +44 20 7612 4342 > > > -----Original Message----- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] > Sent: 20 November 2002 13:55 > To: [EMAIL PROTECTED] > Subject: RE: UTF-16 with Axis > > > 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 > profile: > > 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 > either). > > [1] http://www.ws-i.org/Profiles/Basic/2002-10/BasicProfile-1.0-WGD.htm > > Anne > > > -----Original Message----- > > From: Yates, Danny (ANTS) [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, November 20, 2002 3:52 AM > > To: '[EMAIL PROTECTED]' > > 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: [EMAIL PROTECTED] > > Phone: +44 20 7756 5012 > > Fax: +44 20 7612 4342 > > > > > > -----Original Message----- > > From: Meng Cai [mailto:[EMAIL PROTECTED]] > > Sent: 19 November 2002 19:26 > > To: [EMAIL PROTECTED] > > 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). > ****************************************************************** > ********* > *************************************************************************** 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). ***************************************************************************
