Nadeem I'm surprised you've been told that. I don't believe in that philosophy. I think a service should group a set of related operations. In general, the services I've seen that have one operation are usually of the form:
submit(xsd:Any) The problem with this model is that it reverts to the model where there is no metadata about the schema's of the messages. Alternatively, I've seen the same except where the Schema was one big choice between a number of message formats. Again, I think this is less informative than multiple operations. So, personally, I can't corroborate this model. Paul On Tue, Apr 8, 2008 at 8:29 AM, Hoda, Nadeem [USA] <[EMAIL PROTECTED]> wrote: > > > > I have recently heard that one operation (method/function) per service > (WSDL) is a best practice for SOA/web services. > > Can anyone corroborate this? > > I can see it being cleaner at the WSDL level, but as you expand your service > offerings it will be a maintenance/client headache with dozens of > WSDLs/services for no apparent reason. > > Also, are there good, reliable web service "best practices" guides? > > Thanks, > > Nadeem -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
