File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Web Services and the fly likes Different webservices wsdl at consumer and target Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Different webservices wsdl at consumer and target" Watch "Different webservices wsdl at consumer and target" New topic
Author

Different webservices wsdl at consumer and target

Preet Prasannan.
Ranch Hand

Joined: Feb 09, 2009
Posts: 64
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.


"The more I learn,the more,I get to know, is left to learn."
Preet Prasannan.
Ranch Hand

Joined: Feb 09, 2009
Posts: 64
Any help would be appreciated.
Thanks a lot.
Ivan Krizsan
Ranch Hand

Joined: Oct 04, 2006
Posts: 2198
    
    1
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!


My free books and tutorials: http://www.slideshare.net/krizsan
Preet Prasannan.
Ranch Hand

Joined: Feb 09, 2009
Posts: 64
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.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Different webservices wsdl at consumer and target