• 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

Is SOAP supports "RPC-Literal" or "RPC-Encoded"?

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

I read some documents SOAP(as per BP-1) supports "RPC-Literal" and "Document-Literal". But in some other documents I read as it supports "RPC-Ecoded" and "Document-Literal".
So my question is SOAP supports "RPC-Literal" or "RPC-Encoded"???

Thanks,
George
[ April 21, 2005: Message edited by: George Kennedy ]
 
Author & Gold Digger
Posts: 7617
6
IntelliJ IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In the WSDL 1.1 W3C Note, you will find some extension elements SOAP provides in order to extend WSDL. In the soap:binding extension element, you may specify a style (rpc or document) that will be the default for each contained soap: operation element. Then, in each soap: operation element, you may override the style specified in the soap:binding element. You can thus specify for each operation whether the contained SOAP message is to be considered an RPC message or simply an XML document.

Then, for each SOAP operation you might specify an input, an output and a fault element. In turn, those input, output and fault elements might contain soap:body and soap:header element which feature an attribute named "use" and whose valid values are literal or encoded.

As you can see you can customize each operation along two styles (RPC and Document) and two uses (Literal and Encoded). As a result, the following are all valid couple for SOAP messages:
1. RPC/Literal
2. RPC/Encoded
3. Document/Literal
4. Document/Encoded

However, for compatibility reasons, the Basic Profile 1.0 does not allow the use of Encoded. Thus, in order to be compliant with the Basic Profile you must choose either 1 or 3.
[ April 21, 2005: Message edited by: Valentin Crettaz ]
 
George Kennedy
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Valentin for nice analysis, so we have to use only RPC/Literal or Document/Literal.
 
reply
    Bookmark Topic Watch Topic
  • New Topic