Arguments made by objectors:
- Some WSs may be able to determine the operation name without any
help from the client app
- [Really? Doesn't this mean
that the mechanism is implied in the semantics document?]
- Operation name may be irrelevant to some WSs. Operations
may have been arbitrary groupings of message types.
- [Isn't that an abuse of WSDL?]
- The requirement can be trivially circumvented by a no-op required
feature:
http://example.org/this-extension-satisfies-stupid-requirement
Other potential factors:
- Some companies already use SOAP Action to indicate the desired
action (which may be finer grained than the operation)
- WS-Addressing
uses SOAP Action to specify the desired action
