On Thu, Dec 13, 2007 at 08:26:17AM -0800, Peter Farland wrote: > note that Beta 3 was just released). Note that very recently (build > 189998) further properties were added to the ISOAPDecoder interface to > provide more control over how possibly-reoccuring result parts are > decoded in a response. The existing behavior was preserved, but when we > get more details about your response we'll be able to see whether you > can take advantage of these settings.
What are these settings and what do they affect? The behavior where the webservice call returns an object if it finds a single element versus an array if it finds multiple elements, for an element whose maxOccurs is defined as unbounded in the schema, is driving us insane. -Jeff
