Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <481A4F35.3060303@fluxcorp.com>
Date: Thu, 01 May 2008 17:16:05 -0600
From: Arul Dhesiaseelan <arul@fluxcorp.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: users@cxf.apache.org
Subject: Re: overloaded operation names in JAX-WS
References: <481A499A.90507@fluxcorp.com> <481A4BB4.6060009@dcs.shef.ac.uk>
In-Reply-To: <481A4BB4.6060009@dcs.shef.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks Ian. I am using CXF on both ends. So, your solution works great 
for me.

Cheers,
Arul

Ian Roberts wrote:
> Arul Dhesiaseelan wrote:
>> Hi,
>>
>> I am getting an IllegalArgumentException (An operation with name 
>> [{http://example.com}getGroups] already exists in this service) when 
>> I have overloaded methods in my web service.
>>
>> Is it not supported to have overloaded web service methods in JAX-WS?
>>
>> I have the following methods:
>>
>> public Groups getGroups();
>> public Groups getGroups(String pattern);
>
> No, all the operations must have different names in the WSDL.  If you 
> are using CXF on both client and server side, you can do something like:
>
> @WebMethod
> public Groups getGroups();
>
> @WebMethod(operationName = "getGroupsByPattern")
> public Groups getGroups(String pattern);
>
> This would give the two operations different names in the WSDL, but 
> you can use the Java interface as the serviceClass of a 
> JaxWsProxyFactoryBean and call both methods via their overloaded name.
>
> Ian
>
> P.S. If you were to generate code from the WSDL you would get public 
> Groups getGroupsByPattern(String arg0), of course.
>