Return-Path: Delivered-To: apmail-xml-axis-user-archive@xml.apache.org Received: (qmail 6551 invoked by uid 500); 20 Nov 2002 19:35:08 -0000 Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 6540 invoked from network); 20 Nov 2002 19:35:07 -0000 Message-ID: <006801c290cb$d73327d0$0202a8c0@zermatt> From: "Steve Loughran" To: References: Subject: Re: UTF-16 with Axis Date: Wed, 20 Nov 2002 11:34:05 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > 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: Anne, Who says Axis conforms to the WS-I profile? Its's not like they are some widely recognised standards body like the w3c. Axis (and JAX-RPC) uses stuff that the basic profile doesnt like, specifically rpc/encoded soap by default. Regarding encoding, SOAP is XML, compliant XML parsers all handle UTF-16 encoding. So specification wise, it aint an issue. There is an implementation issue, to wit: what does Axis send down the wire? That is left as experiment to the reader -and remember, you have the source to fix things if they dont work.