As a general rule, you want to avoid returning data as an XML string.
Otherwise, Joe's advice is correct. Your interface should expose simple types, structures of simple types, and arrays of simple types or structures. Avoid returning Java-specific collections. Note that you cannot send or return an array as a primary element (direct child of the SOAP Body) unless the array is wrapped by another element. The SOAP Body may contain at most one child element. An array maps to multiple elements unless you wrap it. Anne On 7/6/07, Joe Nathan <[EMAIL PROTECTED]> wrote:
SOAP meant to be universal over both platforms and programming languages. This means that it's sensible to pass and return values in common datatypes in all platforms and languages which is "String", "Int", "Float". As all SOAP implementations support XML, you may return multiple values wrapped in a xml string. Your client may need to pass arrays imbedded in xml strings! -- View this message in context: http://www.nabble.com/-Axis2--returning-Array-versus-List-%2C-and-more-tf4035642.html#a11474884 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
