WSDL 1.1 Core Spec Issues
Sanjiva Weerawarana
IBM Research
April 12, 2002
Top 5 Issues
- Remove solicit-response and output-only operations
- Remove parameterOrder
- Import/Include
- Message parts (and message itself)
- Services
Solicit-response and Output-only Operations
- WSDL 1.1 defines the abstraction but no bindings
No one is using it (?)
- Multiple interpretations
- Event
- Callback
- Something service needs
Proposal
- Remove solicit-response and output-only operations
For 1.2 WD 1
- Add event mechanism
- Add callback mechanism
Parameter Order
- Optional attribute on
<operation>
- Applicable only for RPC bindings
- Breaks abstraction of portType
Import/Include
- Lot of confusion about how
<import>
is supposed to work
Intent was to model as XSD, but with required location
attribute
- Users also want
<include>
semantics
- Proposal:
Clarify import
Messages
- Should messages exist?
- Should message support optional parts etc.?
- The type/element discussion
Services and Service Types
- Semantics of
<service>
is not clear
-
If you have multiple portTypes, do you have one binding per
portType or more?
- Do you have to put bindings for all portTypes
- Should we allow multiple services per WSDL file?
Proposal
- Introduce service type notion:
ServiceType = name given to a collection or portTypes
- Define
<service>
as something that implements
a serviceTypes
Required to provide exactly one binding per portType