• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Best Practice question

 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am developing a framework of web services that would be given to my team for future development. One of the things I want to do is have a couple of methods that all future webservices support and implement. What is the best way to enforce this? Should I have a "parent" wsdl that all "child" wsdls will import and support? Is there any other way of doing this?

All help much appreciated, thanks!!
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Casey Cox wrote:One of the things I want to do is have a couple of methods that all future webservices support and implement.


What would be the point? Services are supposed to have non-overlapping functional contexts (Agnostic Context, Non-Agnostic Context). By sharing capabilities, the functional contexts would overlap by default. So your attempt is already against "Best Practices".
However all services are supposed to adhere to the Standardized Service Contract principle. See also this post
 
reply
    Bookmark Topic Watch Topic
  • New Topic