Re: * AXIS 1.2 - Stub invokes wrong operation on server side *

[Anne Thomas Manes]

Please keep in mind that SOAP is a *messaging* system, not an RPC system. The SOAP message on the wire has no notion of operation+parameters. All it has is an XML document. And you don't want to overburden the dispatching system on the receiving SOAP node by forcing it to process the entire message before figuring out how to dispatch it. Therefore the dispatching system always works based on the QName of the child element of the SOAP Body. The QName is the message signature.

If you are using Document style, then the signature is the QName of the element referenced in the message part of the input message definition. Each input message must reference a unique element.

If you are using RPC style, then the signature QName is dynamically generated: the namespace comes from the namespace attribute on the <wsdlsoap:body> definition in the binding, and the local name comes from the operation name. WSDL allows you to define multiple operations with the same name, but if you do, you must make sure that the namespaces are different so that you still produce unique QNames.

Anne

On 1/11/06, Jarmo Doc <[EMAIL PROTECTED]> wrote:

Hi Anne, no criticism of your response intended here at all but it's
absolutely maddening how these things came to be.  What could have possessed
anyone to do something like this (base the invocation of operation purely on
the operation's parameters and not on the combination of the operation name
plus its parameters)?  And why hasn't it changed subsequently, now that we
all know it's less than ideal.  Even my cat could have got this one right
;-)

Doubtless, I don't understand the tortured history of SOAP.


>From: Anne Thomas Manes <[EMAIL PROTECTED]>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: Re: * AXIS 1.2 - Stub invokes wrong operation on server side *
>Date: Wed, 11 Jan 2006 08:45:50 -0500
>
>That's the way it works. Each operation must have a unique signature, where
>the signature is the QName of the child element of the SOAP Body. In your
>case, the two operations have identical signatures:
><request:ConflictOfInterestRequest>.
>
>In all cases the request will be routed to the first operation. You must
>define different input elements for each operation.
>
>Anne

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/