Perhaps your senior architect is confusing "operation" with "interface". WSDL 2.0 limits a service (i.e., the thing described by the WSDL) to a single interface. An interface can expose multiple operations, though. The WSDL 2.0 "interface" is equivalent to a WSDL 1.1 "portType". I disagree with the notion that a service should have only one interface (e.g., a service might offer a functional interface and a management interface, and I think the two should be separate), but plenty of other folks believe that it should be one interface per service. Note: WSDL 2.0 supports interface inheritance, so you can define separate interfaces and inherit them into a super interface.
Anne On Tue, Apr 8, 2008 at 1:32 AM, Hoda, Nadeem [USA] <[EMAIL PROTECTED]> wrote: > > Thanks Paul. > > I agree with you totally, and I just wanted to confirm my suspicion. > > > Thanks, > > Nadeem > > -----Original Message----- > From: Paul Fremantle [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 08, 2008 12:21 PM > To: axis-user@ws.apache.org > Subject: Re: WS Best Practice > > > > 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] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
