Can't a web service employ method overloading?  In
Jens' WSDL snippet below, the operations are made
unique by their differing inputs and outputs.  Take
for example, this WSDL:

http://ws.xwebservices.com/XWebBlog/XWebBlog.asmx?wsdl

where the LoadBlog operation is repeated four times. 
This company published their services in our registry
and I was receiving the same "duplicate operation"
error while parsing through some of their WSDLs. I
immediately delved through the code to locate the
problem.  It turns out it was an issue with the WSDL4J
library.

The solution I came up with is explained in the FAQ
here (last question):

http://www.xwebservices.com/Web_Services/XWebBlog/faqs.aspx

Try downloading the modified WSDL4J library and add it
to your path (in lieu of the original WSDL4J jar
file).  I am curious to see if this works with the
full-blown features of Axis.  I posted this issue to
the WSDL4J expert group a couple weeks ago as well.

Regards,

Jeff

>It's invalid WSDL. Operation names must be unique
>within a portType. I
>doubt that this WSDL was generated by .NET.

On 6/2/05, Jens Ahlin <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I have a problem generating java stubs from a wsdl.
I get error message
> Duplicate operation with name=method, found in
portType PortName
> 
> The following part of the wsdl seams to cause the
error:
> 
> 
> <wsdl:portType name="PortName">
>     <wsdl:operation name="method">
>       <wsdl:input name="methodB"
message="tns:methodBSoapIn" />
>       <wsdl:output name="methodB"
message="tns:methhodBSoapOut" />
>     </wsdl:operation>
>     <wsdl:operation name="method">
>       <wsdl:input message="tns:methodASoapIn" />
>       <wsdl:output message="tns:methodASoapOut" />
>     </wsdl:operation>
> ......
> 
> I think the wsdl is generated using MS .NET
> 
> Does anyone know what the problem is ?
> 
> Regards,
> 
> Jens
>


                
__________________________________ 
Discover Yahoo! 
Stay in touch with email, IM, photo sharing and more. Check it out! 
http://discover.yahoo.com/stayintouch.html

Reply via email to