Return-Path: 
 <axis-user-return-31120-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 35762 invoked from network); 28 Feb 2005 23:56:39 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 28 Feb 2005 23:56:39 -0000
Received: (qmail 26137 invoked by uid 500); 28 Feb 2005 23:56:33 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 25981 invoked by uid 500); 28 Feb 2005 23:56:32 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-user@ws.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 25968 invoked by uid 99); 28 Feb 2005 23:56:32 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of atmanes@gmail.com designates
 64.233.170.192 as permitted sender)
Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.192)
  by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 28 Feb 2005 15:56:31 -0800
Received: by rproxy.gmail.com with SMTP id z35so2007586rne
        for <axis-user@ws.apache.org>; Mon, 28 Feb 2005 15:56:29 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=H1ZYeZQWA9lc3dm3OOlJ259OqX8EU3B9Xz+n8VZtw+ZTPc5x/DTjhgLpc+H94CDkO2V8yRcGs+plGi8V18Ka6Yj9yrnTYn3gaXse+8UxmorSPLnOhRqof+Oejh2KkFvwsNA593UnVWXKQiK+Pm9cDdgF9R9dB8fwOr+kKtpHU+o=
Received: by 10.38.171.65 with SMTP id t65mr470588rne;
        Mon, 28 Feb 2005 15:56:29 -0800 (PST)
Received: by 10.38.15.28 with HTTP; Mon, 28 Feb 2005 15:56:28 -0800 (PST)
Message-ID: <bf414ee605022815561e576767@mail.gmail.com>
Date: Mon, 28 Feb 2005 18:56:28 -0500
From: Anne Thomas Manes <atmanes@gmail.com>
Reply-To: Anne Thomas Manes <atmanes@gmail.com>
To: axis-user@ws.apache.org, mtimour-removeit-@gmail.com
Subject: Re: Same signature operations in WSDL
In-Reply-To: <8ae82b12050228123875188a0f@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <8ae82b12050228123875188a0f@mail.gmail.com>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Assuming you are using RPC style, then these two operations do have
unique SOAP signatures, and therefore it is legitimate. In SOAP, the
signature of the message is defined by the QName of the child element
of the SOAP body. Since you have two different operation names, then
the signatures of these operations are intf:op1 and intf:op2.

The problem is that the Axis client runtime can't distinguish these
signatures in Java unless you use different objects in your
application. Hence Axis always interprets your invocation as op1.

Anne


On Mon, 28 Feb 2005 15:38:05 -0500, Timour Mouratov <mtimour@gmail.com> wrote:
> I have a simple question but  I couldn't find an answer on w3.org.
> 
> Can I define  an operations  in WSDL  with same name and identical
> signatures. like this:
> 
> <message name="req">
>         <part name="str"     type="xs:string"/>
> </message>
> <message name="empty"/>
> 
> <portType name="Test">
>       <operation name="op1">
>          <input  name="request"     message="tns:req"/>
>          <output name="response"    message="tns:empty"/>
>       </operation>
>       <operation name="op2">
>          <input  name="request"     message="tns:req"/>
>          <output name="response"    message="tns:empty"/>
>       </operation>
> </portType>
> 
> When I generate the stubs and deploy the service , axis  always calls
> op1 never op2. Is it legitimate from WSDL  specification point of
> view?
> 
> Best regards,
> Timour
>