WSDL Top Issues (Currently)

WSD 1st F2F

Jean-Jacques Moreau

Canon Research, Centre France

Summary

• SOAP 1.2 compatibility
• SOAPAction deprecated
• encodingStyle attribute
• Resived data model and encoding
• RPC
• Extensions (features)
• Message exchange patterns (MEPs)
• Transport binding framework

SOAPAction (Glen, Simon Fell, Jean-Jacques)

• Should not be required for non SOAP bindings
• Should be optional for SOAP 1.2 bindings (deprecated)
• » Implementations SHOULD NOT generate or require SOAPAction UNLESS they have a particular purpose for doing so (e.g., a SOAP Receivers specifies its use) «

SOAP encodingStyle (Rine Holt, Hervé Ruellan)

• SOAP 1.2 or 1.1
• Scoped at element level
• Can be nested
• WSDL 1.1
• Scoped at the message level
• No nesting

SOAP Data Model, Encoding (Jacek, Jean-Jacques)

• SOAP 1.2
• Revised
• Data model (based on graph)
• Encoding
• WSDL 1.1
• Can the revised data model/encoding be described?

SOAP RPC (Hervé Ruellan)

• SOAP 1.2
• RPC is an extension of SOAP
• WSDL 1.1
• Style attribute can only be seen as a hint
• Does not specify
• Which RPC extension is being used
• Which encoding is used for the parameters
• …

SOAP features (Glen Daniels, Hervé Ruellan)

• SOAP 1.2
• Support for extensions (features)
• Semantics extensions named with a URI
• Implemented by
• Either header blocks
• Or message-exchange-patterns (MEPs)
• WSDL 1.1
• Bindings already named by URI…
• … but not extensions

SOAP MEPs (Hervé Ruellan)

• SOAP 1.2
• Message exchange patterns (MEPs)
• Template for the exchange of messages between SOAP Nodes
• WSDL 1.1
• 4 transmissions primitives
• one-way, request-response, solicit-response, notification
• Not able to define which MEP a Web Service will use over a SOAP binding
• Several MEPs can define a one-way transmission primitive

SOAP Transport Binding Framework (Glen Daniels, Hervé Ruellan)

• SOAP 1.2
• Can be transferred over many protocols
• Defines bindings for specifying use of underlying protocols
• E.g. HTTP binding
• WSDL 1.1
• Transport attribute specifies e.g. to use SOAP…
• … but not over which binding
• Also, cannot specify binding options