Win a copy of Spring Boot in Practice this week in the Spring forum!
  • 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
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

proper way to define a WSDL ?

 
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
A WSDL file is an interface over an underlying process.
My question is that what is the proper way to define this interface.
is there just one WSDL file per a process? or there should be distinct WSDL file for each method (sub_process)in the main process?
Thank you for your answer.
 
Rancher
Posts: 43028
76
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
WSDL can define several methods in the same file, which will then be addressed through the same URN. Having different WSDL files thus implies different URNs. Whether that makes sense in your case depends on how closely linked your methods are functionally.
 
Ranch Hand
Posts: 539
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"An interface over an underlying process" is only one view you could take of WSDL - one that'd be encouraged by ideas like BPEL, I'd imagine. You could equally take an RPC view of the world (in the old CORBA sense). In this case, a WSDL can simply be thought of as defining an interface - like the Java interface construct. This should let you apply more familiar design principles to deciding what goes in that interface.

I think of a WSDL as a facade to an application - this takes an RPC-view of Web services, which isn't strictly necessary, but IMO applies to most current uses of Web services. Like a facade, a WSDL (in theory) provides a clean interface to a system, hiding the complexity of implementation. This is the view I use when defining a WSDL.


-Tim
 
reply
    Bookmark Topic Watch Topic
  • New Topic