If you are using a document style service,
you will have to have another method (usually the SoapAction header) to
determine the operation to dispatch to. If the input messages are unique, you
can dispatch on the top level element of the input message.
In RPC style services, a unique operation
name will give you a unique top level element in the SOAP request, so it’s
all good.
--
Tom Jordahl
Adobe ColdFusion Team
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, June 15, 2006
11:41 AM
To: [email protected]
Subject: Re: AXIS1x bug: 2+
operations with same input/output
I understand not having method overloading in the WSDL,
but I question why the Input Message for each Operation must be unique? If
the Operation names are unique, that should be sufficient.
If
two Operations take the same input data but return different results (say one that
returns the results sorted a "natural" way and another that returns
the results in a "hierarchical" manner) shouldn't it be reasonable to
have two Operations with different names that both use the same Input and
Output messages?
If
the Operation names are unique, then the signatures are unique.
Mike McAngus
Associate Chief Engineer, Enterprise
Architecture
Wendy's International, Inc.
One Dave Thomas Boulevard
Dublin, OH
43017
Anne Thomas Manes wrote:
Method overloading should not be exposed through your WSDL interface. You
should define a unique operation name and a unique input message for each
operation. If your service implementation uses method overloading, that's fine
-- but you need to provide an abstraction layer between your WSDL interface and
the service implementation.
The SOAP specification requires that each operation has a unique signature.
(well, technically, it's not required by SOAP 1.1, but it is required by WS-I
Basic Profile and SOAP 1.2. In any case, most SOAP implementations don't
support it.)
Anne
On 6/5/06, Julio César Pérez Arques
<[EMAIL PROTECTED]> wrote:
Thanks for your response.
>
>It's not a bug. Each operation must have a unique signature (defined as the
>qname of the child element of the <soapenv:Body> element).
I think this is a strong limitation.
Then, how can i get methods overloading?
Why is not soapaction used?
Is it the same for Axis2?
Greetings.
Julio César.
>From: "Anne Thomas Manes" <
[EMAIL PROTECTED]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: Re: AXIS1x bug: 2+ operations with same input/output
>Date: Sun, 4 Jun 2006 17:36:43 -0400
>
>It's not a bug. Each operation must have a unique signature (defined as the
>qname of the child element of the <soapenv:Body> element).
>
>Anne
>
>On 6/3/06, Julio César Pérez Arques <[EMAIL PROTECTED]>
wrote:
>>
>>Hello boyz.
>>
>>I am developing a axis ws that has 2 operations with same input/output.
I
>>use axis 1.4 and wsdl2java.
>>But always 1st operation is executed, never the 2nd one.
>>
>>I have read in axis mailing lists it is a bug. Is this correct?
>>I always have read a possible solution in by a user. It dates from
March
>>2006.
>>
>>Is this bug going to fix?
>>
>>Thanks in advance.
>>Julio César.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
