Re: UTF-16 with Axis

2002-11-22 Thread Steve Loughran
- Original Message - From: "Yates, Danny (ANTS)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 22, 2002 12:42 AM Subject: RE: UTF-16 with Axis > Aaah! That makes a difference of course. > > But does Axis serialise its XML using a par

RE: UTF-16 with Axis

2002-11-22 Thread Yates, Danny (ANTS)
ax: +44 20 7612 4342 -Original Message- From: Steve Loughran [mailto:[EMAIL PROTECTED]] Sent: 21 November 2002 17:42 To: [EMAIL PROTECTED] Subject: Re: UTF-16 with Axis - Original Message - From: "Yates, Danny (ANTS)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>

Re: UTF-16 with Axis

2002-11-21 Thread Steve Loughran
- Original Message - From: "Yates, Danny (ANTS)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 21, 2002 3:44 AM Subject: RE: UTF-16 with Axis > Why did it "assume" this? If Google was returning UTF-16, then > a) it should h

Re: UTF-16 with Axis

2002-11-21 Thread Steve Loughran
day, November 21, 2002 3:42 AM Subject: Re: UTF-16 with Axis > As an example, a problem we ran into was using the Google web service, > which returns results in UTF-16. > This caused untold problems in Axis because the parser failed when it > reached an "illegal" charact

Re: UTF-16 with Axis

2002-11-21 Thread easter
Agreed it's probably a Google issue. In fact they do mention it' s going to be an UTF-8 result, however they return as part of this result data coming from outside, for example a resume etc, and they don't encode these objects when they create the message, so sometimes the Axis parser crashes whe

RE: UTF-16 with Axis

2002-11-21 Thread Yates, Danny (ANTS)
44 20 7612 4342 -Original Message- From: easter [mailto:[EMAIL PROTECTED]] Sent: 21 November 2002 11:42 To: [EMAIL PROTECTED] Subject: Re: UTF-16 with Axis As an example, a problem we ran into was using the Google web service, which returns results in UTF-16. This caused untold problems in A

Re: UTF-16 with Axis

2002-11-21 Thread easter
As an example, a problem we ran into was using the Google web service, which returns results in UTF-16. This caused untold problems in Axis because the parser failed when it reached an "illegal" character since it assumed the response was UTF-8. Perhaps you could be a bit more specific about wh

Re: UTF-16 with Axis

2002-11-20 Thread Steve Loughran
- Original Message - From: "Anne Thomas Manes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 20, 2002 14:27 Subject: RE: UTF-16 with Axis > I realize that Axis doesn't currently conform to WS-I Basic Profile, but I > would thi

RE: UTF-16 with Axis

2002-11-20 Thread Anne Thomas Manes
but for the most part, the process is the same.) Anne > -Original Message- > From: Steve Loughran [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 20, 2002 2:34 PM > To: [EMAIL PROTECTED] > Subject: Re: UTF-16 with Axis > > > > > > > Anne wrote: &

Re: UTF-16 with Axis

2002-11-20 Thread Steve Loughran
> 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

RE: UTF-16 with Axis

2002-11-20 Thread Yates, Danny (ANTS)
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

Re: UTF-16 with Axis

2002-11-20 Thread Alex Dovlecel
riginal 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 e

RE: UTF-16 with Axis

2002-11-20 Thread Anne Thomas Manes
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 w

RE: UTF-16 with Axis

2002-11-20 Thread Yates, Danny (ANTS)
, 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 charact

RE: UTF-16 with Axis

2002-11-20 Thread Anne Thomas Manes
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 ge

RE: UTF-16 with Axis

2002-11-20 Thread Yates, Danny (ANTS)
y 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 ca

UTF-16 with Axis

2002-11-19 Thread Meng Cai
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