Mark, Designing a WSDL contract refers to the process of designing your SOAP interface based on the XML messages you intend to exchange (defined using XML Schema) rather than based on the Java interface of your service agent.
The XML Schema type system doesn't support Hashtables, Maps, Lists, etc, therefore your service should not expect to exchange these types. You should define your XML message interface using simple types, structures of simple types, and arrays of simple types and structures of simple types. Structures may contain nested structures. In Java, these structures will map to JavaBeans. They will map to comparable components in other languages. Anne -----Original Message----- From: Mark Chaimungkalanont [mailto:[EMAIL PROTECTED] Sent: Sunday, October 31, 2004 5:44 PM To: [EMAIL PROTECTED] Subject: Re: Maximum Interoperability with "Map" objects I'm quite new to SOAP so I'm not entirely sure what "design WSDL contract" actually entails. Are there any resources out there that you would recommend? I've got a few google hits, but figure that people on this list probably have their "favourite" resources. Is there a collection of such resources somewhare? Cheers Mark C Egor Pervuninski wrote: >Hello, > >## Mark Chaimungkalanont : Fri, 29 Oct 2004 17:07:25 +1000 > >MC> Hi there, I'm writing a SOAP service where interoperability is of >MC> utmost importance. I've read a few of the other posts on this, and >MC> people seem to be saying that Hashtables and the like are not >MC> interoperable. The best strategy seems to be writing a basic >MC> "Entry" bean with key value pairs, using the BeanSerializer and >MC> accepting an Array of them instead of a Map? >MC> >MC> Is this the best way to attack the problem? > >To achieve maximum interoperability, it is better to design WSDL contract >and create program code from it. > >Regards, >Egor Pervuninski >[EMAIL PROTECTED] > > >