• 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

Several services or one? (axis)

 
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have to develop several web services with axis, I'm thinking in two options:

1. Develop all webservices in only a service file. One wsdl, one stub. Very easy.
2. Develop several services in groups. Several wsdl files, several stubs...

What is move easy and clear, for the client developer?
Thanks
 
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well, IMHO, what is easy for the developer isnt always the perfect way, right? If your web services have different functionalities and are distinct entities, it makes sense to separate them. Anyway the WSDL has to go over the net and the "small-is-beautiful" principle applies..

Of course, I could be wrong.

 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Also there is the issue of version control. Publishing multiple services in the same WSDL inexorably links them to one another - something you want to avoid. As you evolve your services you may have to publish multiple versions of the interface to the same service for backward compatibility and each client installation may require a different version mix of the different endpoints, potentially leading to a combinatorial explosion of customized WSDLs.
Bottom-line - stick with the smallest WSDLs possible - but no smaller.

You can usually manage common portions between WSDLs with XSD and WSDL imports. But again make sure to include a version identifier in your import filenames.
WSDL file imports
[ July 12, 2006: Message edited by: Peer Reynders ]
 
reply
    Bookmark Topic Watch Topic
  • New Topic