> -----Original Message-----
> From: Scott Nichol [mailto:[EMAIL PROTECTED]]
>
> Thanks for getting us back to the original topic. Are you
> saying that you would like to have more of the Java data
> structure interfaces and classes (e.g. Collection, Map,
> subinterfaces and classes implementing them) registered with
> [de-]serializers internally, so that you don't have to think
> about them when you are coding, e.g. to remember to specify
> Map.class rather than just using myMap.getClass()? That
> seems pretty reasonable. I think that the absence of this is
> mostly historical. Until recent releases, Apache SOAP
> compiled and ran on JDK 1.1, so only Hashtable and Vector had
> built-in [de-]serializers. (And I notice that it is
> Hashtable, not Dictionary, so that Hashtable users did not
> have to always specify Dictionary.class as the Java type.) I
> will look at adding the other mappings.
Scott,
Does this raise any issues for folks that may want to send and receive
SOAP via a device using the MIDP (which doesn't have Collections)? I'm
thinking of situations where 1.2 level systems are sending Collection
structures into MIDP devices, which I imagine won't be able to
deserialize them.
regards,
Bill de hÓra
..
Propylon
www.propylon.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
