serializers vs. deserializer factories

[Doug Davis <du...@us.ibm.com>]

Just wondering...from looking at the code and the samples it appears that
for serializers we just give Axis a class but for deserializers Axis wants
a deserializer factory - why the inconsistency?  Why wouldn't we want to
use the same mechanism for both?  My best guess is that desers might want
to save state and serializers typically won't so a single instance of a
serializer will do.  Can someone confirm this - or let me know the real
reason if I'm wrong.
-Dug

Re: serializers vs. deserializer factories

[Glen Daniels <gd...@macromedia.com>]

Precisely correct.  We've discussed attempting to make deserializers
stateless as well, which may happen at some point, but for now the easiest
way to deal with them is making a new one for each element.

----- Original Message -----
From: "Doug Davis" <du...@us.ibm.com>
To: <ax...@xml.apache.org>
Sent: Sunday, July 29, 2001 1:23 PM
Subject: serializers vs. deserializer factories


> Just wondering...from looking at the code and the samples it appears that
> for serializers we just give Axis a class but for deserializers Axis wants
> a deserializer factory - why the inconsistency?  Why wouldn't we want to
> use the same mechanism for both?  My best guess is that desers might want
> to save state and serializers typically won't so a single instance of a
> serializer will do.  Can someone confirm this - or let me know the real
> reason if I'm wrong.
> -Dug
>