[ 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
