Both methods provide a place to get custom serializer/deserializer.
In both cases the Base(De)SerializerFactory looks for these methods to get
the serializer /deserializer.
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Glen Daniels
<gdaniels@macrome To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
dia.com> cc:
Subject: RE:
getSerializer/getDeserilizer methods in the Bean
03/28/2002 12:20
PM
Please respond to
axis-dev
Interesting stuff!
So, I get how getSerializer() might work - you've got a Class you're
serializing, so you can just use that instead of going to the TypeMapping.
I don't understand getDeserializer, though - when could/would that get
used?
--Glen
> -----Original Message-----
> From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 28, 2002 1:15 PM
> To: [EMAIL PROTECTED]
> Subject: getSerializer/getDeserilizer methods in the Bean
>
>
> Some cool changes I am working on.
>
> I am adding getSerializer/getDeserializer methods in the java bean (or
> _Helper).
>
> These methods construct the corresponding
> serializer/deserializer (passing
> in the TypeDesc meta data).
>
> This change prevents unnecessary introspection and gives
> users a place to
> hang their own custom serializer/deserializer.
>
> I also made some cosmetic changes to make it easier to extend
> some of these
> classes.
>
> Rich Scheuerle
> XML & Web Services Development
> 512-838-5115 (IBM TL 678-5115)
>
