RE: message part in document/literal style

[thomas . cherel]

I had a discussion with some of those guys some times ago about this issue. The problem is when you look at the SOAP/WSDL spec, the exact way of producing the SOAP body in a doc/lit with multiple parts is weird/wrong (some statements in the spec make it really weird by saying that the soap body element itself is of multiple xml type). I think this also the reason why .NET has this notion of doc/wrapped to workaround the issue. I think it is better defined in SOAP/WSDL 1.2.   Thomas   -----Original Message----- From: Wei Chen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 05, 2003 2:55 PM To: [EMAIL PROTECTED] Subject: RE: message part in document/literal style   I submitted a test case to axis-dev but nobody responded. Sounds like I should submit a bug report.   - Wei Chen   -----Original Message----- From: Glen Daniels [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04, 2003 8:59 PM To: '[EMAIL PROTECTED]' Subject: RE: message part in document/literal style   I don't think WSDL prohibits it.  You'd get something like:   <SOAP:Body>   <part1>...</part1>   <part2>...</part2> </SOAP:Body>   Most WSDLs use a single part for doc/lit services, and indeed Axis doesn't deal with multiple parts like this very well.   --Glen -----Original Message----- From: Wei Chen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04, 2003 8:51 PM To: [EMAIL PROTECTED] Subject: message part in document/literal style Hi,   If an operation is document/literal style, can the input/output message have multiple parts? Axis doesn't seem working if the message has multiple parts. But I can not find anything about this in WSDL spec.   Any help is appreciated.   - Wei Chen