W3C home > Mailing lists > Public > public-ws-addressing@w3.org > July 2005

Explicit Association of wsa:Action values to an operation's messages

From: Ruchith Fernando <ruchith.fernando@gmail.com>
Date: Mon, 18 Jul 2005 11:59:11 +0000
Message-ID: <559c463d05071804591f4a2758@mail.gmail.com>
To: public-ws-addressing@w3.org
Cc: Sanjiva Weerawarana <sanjiva@opensource.lk>

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"

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 :-)

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 Tuesday, 19 July 2005 04:38:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:10 UTC