----- Original Message ----- From: "Peter Norrhall" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 14, 2003 01:39 Subject: Re: Hashtable : how to map it
> Hello, > > I have been following this newsgroup for a couple of weeks now. And this > type of question always comes up. The best thing always seems to be to > create an array as output. In that way you rather safe regarding > interoperability. Anyone that has another opinion? my opinion is 'It'd be nice if everything understood hashtable, list, and a few other core data structures', but they dont, at least not consistently. > > Isn't it so that if one would like to have interoperability the best way > to go is to use Document style calls instead RPC? Is that why .Net use > Document as default? Someone said that Document style is the default > regarding to SOAP 1.2, but I can't find that statement within the spec. the WS-I basic profile lays down that Document style is the future. It appeals because it (a) looks nicer, especially if you write the XSD first, and (b) should be more maintenance friendly; you can add stuff to the schema if you started off right. But Axis works best with JAX-RPC, currently. > I have one thing that concerns about Document style binding and that is > encoding. From what I understand there is no way to change the UTF-8 > encoding for a SOAP request. In one case we solved, using RPC style > binding, returning a String that was a complete XML-document with a > different encoding. Other ways? base64, attachments. But you dont have interop of attachments across all implementations either... -steve
