WSDL 1.2 Binding Changes - PowerPoint PPT Presentation

1 / 8
About This Presentation
Title:

WSDL 1.2 Binding Changes

Description:

Without message we can make WSDL 1.2 bindings dramatically simpler. Overview ... Make _at_interface optional to make binding more reusable binding name='ncname' ... – PowerPoint PPT presentation

Number of Views:54
Avg rating:3.0/5.0
Slides: 9
Provided by: sanjivawe
Category:
Tags: wsdl | binding | changes | make

less

Transcript and Presenter's Notes

Title: WSDL 1.2 Binding Changes


1
WSDL 1.2 Binding Changes
  • Sanjiva Weerawarana
  • WSDL WG F2F July 2003
  • Raleigh, NC

2
Motivation
  • Without ltmessagegt we can make WSDL 1.2 bindings
    dramatically simpler

3
Overview
  • ltbindinggts in general
  • SOAP binding
  • HTTP binding
  • _at_encodingStylerpc
  • General documents

4
ltwsdlbindinggt
  • Make _at_interface optional to make binding more
    reusable
  • ltbinding namencname interfaceqname gt
  • binding details
  • ltoperation nameqnamegt .. lt/operationgt
  • lt/bindinggt
  • If any ltoperationgt elements are present, then
    _at_interface MUST be present
  • service/_at_interface MUST match deref(endpoint/_at_bind
    ing)/_at_interface
  • Allow ltendpointgt to point to bindings or inline
    bindings
  • ltservice interfaceqnamegt
  • ltendpoint namencname
  • bindingslist-of-qnamesgt
  • inlined-bindings
  • address-binding
  • lt/endpointgt
  • lt/servicegt

5
SOAP Binding
  • Define default SOAP binding rules
  • _at_body goes into ltsoapBodygt
  • Each of _at_headers goes into ltsoapHeadergt
  • Define new binding element for default rule for
    wsoapoperation/_at_soapActionURI
  • Proposal interfaceTNSoperation-name
  • Drop ltwsoapbodygt, ltwsoapfaultgt
  • Change ltwsoapheadergt add new header or add
    _at_role/_at_mustUnderstand
  • Drop _at_type, _at_namespace, _at_localname,
    _at_encodingStyle
  • Add _at_mustUnderstand??
  • Retain ltwsoapheaderFaultgt update
  • Drop ltsoapbindinggt drop _at_protocol
  • Change ltsoapaddressgt add _at_protocol
  • Cool feature No need to pay attention to
    /definitions/interface/operation/_at_encodingStylerp
    c

6
HTTP Binding
  • For _at_encodingStylerpc case
  • If types are all simple, then can do HTTP
    GET/POST binding for content-typeform-url-encoded
  • URL rewriting, POST body,
  • Basically s!_at_partfoo!xpath/foo!g
  • For other cases
  • Natural text/xml binding with input/_at_body as
    input payload and output/_at_body as output payload

7
Example - Today
  • ltdefinitionsgt
  • lttypesgt
  • ltxsdschemagt
  • element-decls
  • lt/xsdschemagt
  • lt/typesgt
  • ltinterfacegt
  • ltoperation namencnamegt
  • ltinput elemente1/gt
  • ltoutput elemente2/gt
  • lt/operationgt
  • lt/interfacegt
  • ltbinding namencname
  • interfaceqnamegt
  • ltsoapbinding transporthttp/gt
  • lt/bindinggt
  • ltservice interfacencnamegt
  • ltendpoint namencname
  • bindingqnamegt
  • ltsoapaddress location/gt
  • lt/endpointgt
  • lt/servicegt
  • lt/definitionsgt

8
Example - Tomorrow
  • ltdefinitionsgt
  • lttypesgt
  • ltxsdschemagt
  • element-decls
  • lt/xsdschemagt
  • lt/typesgt
  • ltinterfacegt
  • ltoperation namencnamegt
  • ltinput elemente1/gt
  • ltoutput elemente2/gt
  • lt/operationgt
  • lt/interfacegt
  • ltbinding namefoogt
  • ltsoapbinding/gt
  • lt/bindinggt
  • ltservice interfacencnamegt
  • ltendpoint namencname
  • bindingxfoogt
  • ltsoapaddress protocol..
  • location/gt
  • lt/endpointgt
  • lt/servicegt
  • lt/definitionsgt
Write a Comment
User Comments (0)
About PowerShow.com