intertwingly

It’s just data

null


Patrick Logan writes:

Static languages typically rely on "outside" tools to generate such code, (i.e. IDL compilers).

In several SOAP implementations, including Axis, you can also do the reverse.  Write the service and we will generate the WSDL to match.  Want to take a look at how easy it can be?

XML-RPC is so simple that it is possible to define mappings from many data types into XML-RPC. But it is best to define one mapping from XML-RPC to just some of the native languages data types. (E.g. many Java collection classes could map to an XML-RPC array, but an XML-RPC array should map back to just one of those collection classes.)

SOAP is so complicated that, well, it's questionable whether a single language mapping between SOAP and a Java-like language is worthwhile.

In Axis, multiple Java data types can map to an array.  And by using introspection on the target service, we will determine what data type to map the array back to. 

The tools I use work pretty well.

Cool!