The SOAP 1.1 spec lets you name things as you choose. Many products use a <methodName> element to encapsulate the request, and many use <methodNameResponse> to encapsulate the response. There are *many* variations on how to name the return value. The Apache SOAP <return> seemed common a few years ago, but <methodNameReturn> or <methodNameResult> seem popular now, maybe because Microsoft uses those.
Since Apache SOAP does not support output parameters, it always just treats the first child of the response element as the return value. I don't recall whether the SOAP 1.1 spec required such behavior, but that's how it's done. In today's preferred practice, as specified by WS-Interop, you would always have WSDL, which will specify element names so each side of the conversation should know what the other side expects. On 3 Jul 2003 at 8:05, Steve Pruitt wrote: > Understood. Doesn't this make it a bit dicey when parsing out the response data? I > have noticed that axis does something like <methodnameResponse>...<methodnameReturn> > ...... > Whereas apache SOAP featured ....<return>..... > Each vendor could do something different. Appending methodname to Response and > Request is good practice. But no guarantee? > > -Steve Pruitt > > > > -----Original Message----- > From: Scott Nichol [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 02, 2003 11:51 PM > To: [EMAIL PROTECTED] > Subject: Re: response and result tag override > > > I will qualify my previous response by saying there is no way built > into the SOAP protocol. You could, of course, have a service that > accepted as parameters the response and result element names. > However, since such a response could not be described in WSDL, your > service would not be following WS-Interop guidelines. > > On 2 Jul 2003 at 13:28, Steve Pruitt wrote: > > > All, > > > > Is there away in a soap request to specify what the response and result tags are > > named in the soap response? > > > > > > Thanks, > > > > -Steve Pruitt > > > > > Scott Nichol > > Do not reply directly to this e-mail address, > as it is filtered to only receive e-mail from > specific mailing lists. > > > Scott Nichol Do not reply directly to this e-mail address, as it is filtered to only receive e-mail from specific mailing lists.
