tags:

views:

74

answers:

1

I'm looking for some pros and cons of creating one operation per wdsl against bundling operations in a single wdsl

Small example below:

  <operation name="Divide">
     <input message="y:DivideMessage"/>
     <output message="y:DivideResponseMessage"/>
  </operation>

instead of being divide and this were more complex operations, what are the pros/cons of having a one wsdl per operation

+1  A: 

I'm not sure I understand the question... But if you ask about putting all operations in a single WSDL or each in one WSDL...

I think the better is to keep all in one single WSDL if the operations are on the same endpoint, as many tool will allow you to generate a Web service client from the WSDL : using a single WSDL you can then generate a client that will be able to call all the operations. While if the operations are in separate WSDL you will have to generate several clients, one per operation which will be uncomfortable to use...

Vinze