char is very platform dependant. Java is lucky in that it's
implementation can handle many locales - Western, Chinese,
Japanese, etc - not all platforms can do this.
Additionally, any char passed even between Java servers would
have to define the locale for the chars (possibly each char).
Andy.
> -----Original Message-----
> From: clearthink [mailto:[EMAIL PROTECTED]]
> Sent: 20 September 2001 02:59
> To: [EMAIL PROTECTED]
> Subject: char encoder/decoder
>
>
> This question has already been asked but
> no replies have been forthcoming. how in
> the heck is it the case that apache soap
> handles all build-ins but not char?
>
> what is the solution? what is the work
> around? in my application i keep getting:
>
> No Serializer found to serialize a 'char' using
> encoding style 'http://schemas.xmlsoap.org/soap/encoding/'
>
> this is like coming to work with no clothes on!
>
> i thought it was pilot error but when i examined
> the API closer, i can see that indeed no serializer/
> deserializer is included - although all other built-ins
> seem to be.
>
> thanks!
> shane
>