- From: Francisco Curbera <curbera@us.ibm.com>
- Date: Tue, 19 Jul 2005 23:25:14 -0400
- To: Ruchith Fernando <ruchith.fernando@gmail.com>
- Cc: public-ws-addressing@w3.org, public-ws-addressing-request@w3.org, Sanjiva Weerawarana <sanjiva@opensource.lk>
WSA does not require a one to one mapping between Action values and WSDL
operation messages. I happen to think that such a mapping is a good design
practice but clearly not everyone shares that view (as past WG discussions,
and WS-Trust, show).
OTOH, the wsa:Action attribute need not be explicitly assigned in the WSDL.
This again is a good practice, but the fact is that Action values are often
defined by protocol specs (as WS-Trust). There are many possible sources of
Action values, not just WSDL.
Paco
Ruchith Fernando
<ruchith.fernando@gmail. To: public-ws-addressing@w3.org
com> cc: Sanjiva Weerawarana <sanjiva@opensource.lk>
Sent by: Subject: Explicit Association of wsa:Action values to an operation's messages
public-ws-addressing-req
uest@w3.org
07/18/2005 07:59 AM
Please respond to
Ruchith Fernando
Hi all,
I have a question about the Web Services Addressing 1.0 - WSDL Binding [1].
Section 3.1 Explicit Association states that in the case of wsdl 1.1
we should specify the wsa:Action values for the messages in the
operation element's input and output child elements in the
wsdl:portType element.
WS-Trust specification[3] defines a SecurityTokenService (wsdl [2])
which has a wsdl:portType called "SecurityTokenService".
There is a "RequestSecurityToken" operation defined in this portType.
There are 4 types of requests: issuance, validation, renewal and
cancellation that can be consumed by the same "RequestSecurityToken"
operation.
BUT the WS-Trust spec[3], requires the use of different wsa:Action
values for each of the input/output messages for those different
behaviors. The spec calls each one of the behaviors 'binding's which
made me think that it expects different wsdl:bindings of the
"SecurityTokenService" portType for each of the different behaviors.
But according to [1] it not possible to associate wsa:Action values
with the input/output element in the wsdl:binding.
Is this behaviour expected by the WS-Trust spec incorrect?
Am I correct if I say that, to have n different wsa:Action values for
the input messages' operation 'foo' we have to have n different
wsdl:portType definitions in the wsdl?
Please correct me if I have missed something :-)
Thanks,
Ruchith Fernando
[1] http://www.w3.org/TR/2005/WD-ws-addr-wsdl-20050413/
[2]
http://www-128.ibm.com/developerworks/library/specification/ws-trust/ws-trust.wsdl
[3] ftp://www6.software.ibm.com/software/developer/library/ws-trust.pdf
Received on Wednesday, 20 July 2005 03:25:21 UTC