4177Re: [soapbuilders] Re: Where's decimal?
- Jul 3, 2001
> For anything in Java that implements List, I think the naturalThis is the approach we take. Any Collection (Set, List, Vector) in java
> is a SOAP array. Then it's up to the tools on either side to correctly
> translate between whatever linear-ordinal-collection class you have
> SOAP arrays.
is serialized as an array. It is up to the client and server to sort out
what was required on deserializing. The WSDL reflects that it is an array
of anyType. This means that any client can talk to us with these datatypes
without problem as long as it supports arrays (which is a given).
Equally importantly, it also means that a VB programmer doesn't need to
worry about Java datatypes. I don't want someone coding to my Web
Service to worry about language specifics of the implementation. It
should be exposed as standard types where possible and any required
mapping to the underlying implementation done on the server.
I think defining specific SOAP types for these java specific types is a
mistake as SOAP should not have to worry about these higher level language
> Maps are a bit harder. The Apache team came up with a serialization forWe use the same encoding for Map as Apache and Paul. Seems pretty sensible!
> Java Hashtables last year which Paul also implements in SOAP::Lite.
> essentially a SOAP compound type which is a list of name->value pairs:
Graham raised this a few weeks ago and got pretty much this response I think,
but appears not to like it so has sneaked it in to another thread ;-)
- << Previous post in topic Next post in topic >>