• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

WSDL Style?  RSS feed

 
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am trying to read web services. I came across the WSDL binding styles in the following article

http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/

After reading this article I understood that each style has advantage and disadvantage.
Which factor drive towards the WSDL Style? Meaning, Is architect/developer drives the decision to choose which one to use based advantages and disadvantages? How is this going to work in production environment.
I am so sorry if this is stupid question?
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

vishnu moorthy wrote:Is architect/developer drives the decision to choose which one to use based advantages and disadvantages?



Currently there is actually less choice than the article suggests.

  • Most current generation SOAP web service stacks don't even support the rpc/encoded messaging mode anymore - so if you have to consume to an existing rpc/encoded SOAP web service you usually have to employ a previous generation SOAP client web service stack and pray that it interoperates with the existing web service.


  • rpc/literal was popular for a while because it is more interoperable but generally has fallen out of favor because only the parameters can be validated using standard XML schema tools (e.g. a validating parser) - if you want to validate the entire SOAP body your tools would have to be WSDL aware.


  • document/literal is the "de facto" standard for a modern SOAP web service. You send a single "document" to the endpoint and the endpoint routes the "document" to the "web method" (operation) that is responsible for processing that "type of document" (i.e. no operation overloading, as the name of the operation is irrelevant to the consumer-provider interaction). If the operation uses an in-out (request-response) message exchange pattern (MEP) you get a single response document back. The SOAP body can be fully validated with a standard validating XML parser.


  • Because some people simply cannot let go of the RPC paradigm (and to accomodate tools that generate the web service contract (WSDL) from code - which is considered by some an anti-pattern) there is the wrapped document/literal convention which basically replaces of the rpc messaging style while using the document messaging style.

  •  
    vibeeshan kambli
    Ranch Hand
    Posts: 41
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Peer, Thanks for the informative reply.
    • Post Reply Bookmark Topic Watch Topic
    • New Topic
    Boost this thread!