Uploaded image for project: 'Apache Taverna'
  1. Apache Taverna
  2. TAVERNA-291

WSRF support: WS-Addressing ''To'' request header is missing

    XMLWordPrintableJSON

Details

    • Bug
    • Status: To Do
    • Minor
    • Resolution: Unresolved
    • None
    • None

    Description

      The WSRF support (T2-270) does not send the ws:To header - which means Globus on the server side will print out:

      2009-06-17 10:49:23,641 WARN handlers.FaultHandler [ServiceThread-6,getFrom:114] The WS-Addressing ''To'' request header is missing

      This is only a warning message, and does not normally affect invocation of the service, but it can confuse debugging of other problems.

      Adding a naive support for this should be easy, just providing the same address in the To-field as to where the soap action is currently invoking. (If I understand the WS Addressing correctly). The other wsa-headers (MessageID and Action) should probably also be provided.

      Example from the response from the server:

         <soapenv:Header>
            <wsa:MessageID soapenv:mustUnderstand="0">uuid:87b402f0-7450-11dd-bfbb-882dcdf2cc70</wsa:MessageID>
            <wsa:To soapenv:mustUnderstand="0">http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa:To>
            <wsa:Action soapenv:mustUnderstand="0">http://counter.com/CounterPortType/addResponse</wsa:Action>
         </soapenv:Header>
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            stain Stian Soiland-Reyes
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:

              Time Tracking

                Estimated:
                Original Estimate - 4h
                4h
                Remaining:
                Remaining Estimate - 4h
                4h
                Logged:
                Time Spent - Not Specified
                Not Specified