Axis2
  1. Axis2
  2. AXIS2-53

Binding wsa:Action values to an operation's messages

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.92
    • Component/s: kernel
    • Labels:
      None

      Description

      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>

        Activity

        Hide
        Srinath Perera added a comment -

        Yes this is a shortcomming of the corrent impl. +1 for fix this. But shall we make this post 0.9.?

        Show
        Srinath Perera added a comment - Yes this is a shortcomming of the corrent impl. +1 for fix this. But shall we make this post 0.9.?
        Hide
        Srinath Perera added a comment -

        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?

        Show
        Srinath Perera added a comment - 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?
        Show
        Ruchith Fernando added a comment - http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200507.mbox/%3c559c463d05070802186c7b0859@mail.gmail.com%3e
        Hide
        Ruchith Fernando added a comment -

        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/

        Show
        Ruchith Fernando added a comment - 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/
        Hide
        Ruchith Fernando added a comment -

        Can someone please change the name of this issue to
        'Binding wsa:Action values to an operation's messages'

        thanks
        Ruchith

        Show
        Ruchith Fernando added a comment - Can someone please change the name of this issue to 'Binding wsa:Action values to an operation's messages' thanks Ruchith
        Hide
        Ruchith Fernando added a comment -

        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.

        Show
        Ruchith Fernando added a comment - 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.
        Hide
        Srinath Perera added a comment -

        To complete the senario, we need to complete the operation dispatching based on ws:action ...assigining it to our wsdl guru

        Show
        Srinath Perera added a comment - To complete the senario, we need to complete the operation dispatching based on ws:action ...assigining it to our wsdl guru
        Hide
        Eran Chinthaka added a comment -

        Fixed.
        Mapping can now be defined as a parameter under the operation.
        <operationname="" >
        <parameter name="Mapping">here goes the new mapping</parameter>
        ...................
        </operation>

        Show
        Eran Chinthaka added a comment - Fixed. Mapping can now be defined as a parameter under the operation. <operationname="" > <parameter name="Mapping">here goes the new mapping</parameter> ................... </operation>
        Hide
        Eran Chinthaka added a comment -

        Sorry parameter should be as follows :

        <operationname="" >
        <parameter name="wsamapping">here goes the new mapping</parameter>
        ...................
        </operation>

        Show
        Eran Chinthaka added a comment - Sorry parameter should be as follows : <operationname="" > <parameter name="wsamapping">here goes the new mapping</parameter> ................... </operation>

          People

          • Assignee:
            Chathura Herath
            Reporter:
            Ruchith Fernando
          • Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development