You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ruchith Fernando (JIRA)" <ji...@apache.org> on 2005/06/29 13:41:58 UTC
[jira] Created: (AXIS2-53) Binding service operations to wsa:Action
Binding service operations to wsa:Action
----------------------------------------
Key: AXIS2-53
URL: http://issues.apache.org/jira/browse/AXIS2-53
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: core
Reporter: Ruchith Fernando
An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
Example:
<operation name="RequestSecurityToken">
<messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
<action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
<action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
<action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
<action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
</operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-53) Binding wsa:Action values to an operation's messages
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=all ]
Srinath Perera updated AXIS2-53:
--------------------------------
Summary: Binding wsa:Action values to an operation's messages (was: Binding service operations to wsa:Action)
> Binding wsa:Action values to an operation's messages
> ----------------------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-53) Binding service operations to wsa:Action
Posted by "Ruchith Fernando (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=comments#action_12316645 ]
Ruchith Fernando commented on AXIS2-53:
---------------------------------------
According to the W3C-Addressing folks we do NOT have to bind multiple wsa:Action values to the same message in an operation.
http://lists.w3.org/Archives/Public/public-ws-addressing/2005Jul/0134.html
Therefore we can stick to what is defined in http://www.w3.org/TR/2005/WD-ws-addr-wsdl-20050413/
Can someone please close this issue. :-)
> Binding service operations to wsa:Action
> ----------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AXIS2-53) Binding wsa:Action values to an operation's messages
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=all ]
Srinath Perera reassigned AXIS2-53:
-----------------------------------
Assign To: Chathura Herath
To complete the senario, we need to complete the operation dispatching based on ws:action ...assigining it to our wsdl guru
> Binding wsa:Action values to an operation's messages
> ----------------------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
> Assignee: Chathura Herath
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-53) Binding service operations to wsa:Action
Posted by "Ruchith Fernando (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=comments#action_12315902 ]
Ruchith Fernando commented on AXIS2-53:
---------------------------------------
Can someone please change the name of this issue to
'Binding wsa:Action values to an operation's messages'
thanks
Ruchith
> Binding service operations to wsa:Action
> ----------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-53) Binding service operations to wsa:Action
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=comments#action_12315210 ]
Srinath Perera commented on AXIS2-53:
-------------------------------------
How does this is supported in the WSDL1.1/WSDL 2.0 ..
My understanding is more than one action for a operation is not supported by WSDL and if that is case we can just do
with one Action. So I purpose
<operation name="foo" action="bar" ...>
...........
</operation>
thoughts?
> Binding service operations to wsa:Action
> ----------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS2-53) Binding wsa:Action values to an operation's messages
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=all ]
Eran Chinthaka resolved AXIS2-53:
---------------------------------
Fix Version: 0.92
Resolution: Fixed
Fixed.
Mapping can now be defined as a parameter under the operation.
<operationname="" >
<parameter name="Mapping">here goes the new mapping</parameter>
...................
</operation>
> Binding wsa:Action values to an operation's messages
> ----------------------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
> Assignee: Chathura Herath
> Fix For: 0.92
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-53) Binding service operations to wsa:Action
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=comments#action_12314678 ]
Srinath Perera commented on AXIS2-53:
-------------------------------------
Yes this is a shortcomming of the corrent impl. +1 for fix this. But shall we make this post 0.9.?
> Binding service operations to wsa:Action
> ----------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-53) Binding service operations to wsa:Action
Posted by "Ruchith Fernando (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=comments#action_12315288 ]
Ruchith Fernando commented on AXIS2-53:
---------------------------------------
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200507.mbox/%3c559c463d05070802186c7b0859@mail.gmail.com%3e
> Binding service operations to wsa:Action
> ----------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-53) Binding wsa:Action values to an operation's messages
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=comments#action_12323311 ]
Eran Chinthaka commented on AXIS2-53:
-------------------------------------
Sorry parameter should be as follows :
<operationname="" >
<parameter name="wsamapping">here goes the new mapping</parameter>
...................
</operation>
> Binding wsa:Action values to an operation's messages
> ----------------------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
> Assignee: Chathura Herath
> Fix For: 0.92
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-53) Binding service operations to wsa:Action
Posted by "Ruchith Fernando (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-53?page=comments#action_12315537 ]
Ruchith Fernando commented on AXIS2-53:
---------------------------------------
This is the wsdl given in the WS-Trust [1] specification
http://www-128.ibm.com/developerworks/library/specification/ws-trust/ws-trust.wsdl
If my interpretation is correct, the spec requires different bindings of the 'SecurityTokenService' portType definition to be used for security token issuance, validation, renewal and cancellation. And each of those bindings specify their own pair of wsa:Action values to be used with the input message and the output message.
How can this be facilitated with WSDL/WS-Addressing [2] binding spec, where wsa:Action values are associated with the 'portType' definition in the wsdl?
Is this a problem with the WS-Trust spec... or have I have missed something obvious :-)
[1] ftp://www6.software.ibm.com/software/developer/library/ws-trust.pdf
[2] http://www.w3.org/TR/2005/WD-ws-addr-wsdl-20050413/
> Binding service operations to wsa:Action
> ----------------------------------------
>
> Key: AXIS2-53
> URL: http://issues.apache.org/jira/browse/AXIS2-53
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: core
> Reporter: Ruchith Fernando
>
> An operations should be able to handle different types of wsa:actions. Therefore there can be a set of actions wsa:actions associated with an oprtation.
> Therefore we will have to provide a mechanism of mapping wsa:action uri values to the service oprtations.
> One option is to have a list of wsa:action URIs to be listed in the service.xml with respect to a given operation.
> Example:
> <operation name="RequestSecurityToken">
> <messageReceiver class="org.apache.axis.receivers.RawXMLINOutMessageReceiver"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate"/>
> <action uri="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel"/>
> </operation>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira