• 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

Different webservices wsdl at consumer and target

 
Ranch Hand
Posts: 64
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I have a requirement where in I need to support multiple applications hosting wsdls where is my application will be consuming their wsdls.
Now the issue is lets say application A "adds"some new operation to wsdl and B doesnt,and I reflect the change in the client in my application, will it create problem while consuming the wsdl from application B?
Also what are the rules that govern wsdls? If the host wsdl have less operations and the client is generated on a wsdl with more number of operations, will it create a problem?
Do all the operations and the elements need to be same on both side.
Or it that only the operations that may be used by the client should be exactly similar and others can be different?
Please suggest.

 
Preet Prasannan.
Ranch Hand
Posts: 64
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Any help would be appreciated.
Thanks a lot.
 
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi!
One approach is to use a document-based web service.
Adding a new service or "operation" would then be a matter of adding a new document the service accepts, while retaining all the old.
Each document will have an unique namespace, which is how the service determines how to process the document submitted.

Alternatively, if you have a WSDL and some XML schemas and only adds optional data with default values to the XML schemas and/or new operations to the WSDL, then you will be able to retain backwards compatibility with old clients. The key here is never to remove anything and never to add new things that are required, since that would break old clients.
Best wishes!
 
Preet Prasannan.
Ranch Hand
Posts: 64
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks a lot Ivan. I am trying out the different scenarios and then post back when I face any issues.
Thanks a lot for the help.
 
reply
    Bookmark Topic Watch Topic
  • New Topic