SwitchYard
  1. SwitchYard
  2. SWITCHYARD-703

Propagate message headers between switchyard and riftsaw

    Details

    • Type: Feature Request Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      Currently only the message content is passed in and out of the bpel component. However for transaction and security purposes, it will be necessary for the header information to be passed between switchyard and riftsaw.

        Gliffy Diagrams

          Issue Links

            Activity

            Gary Brown created issue -
            Gary Brown made changes -
            Field Original Value New Value
            Assignee Ivo Bek [ ibek ]
            David Ward made changes -
            Link This issue depends SWITCHYARD-710 [ SWITCHYARD-710 ]
            Hide
            David Ward added a comment -

            I believe that SWITCHYARD-710 should be resolved on it's own as a prerequisite to this issue.

            Show
            David Ward added a comment - I believe that SWITCHYARD-710 should be resolved on it's own as a prerequisite to this issue.
            David Ward made changes -
            Hide
            David Ward added a comment - - edited

            SWITCHYARD-710 has been pushed. Now:

            1. Set the soapHeadersType: <binding.soap><contextMapper includes=".*" soapHeadersType="DOM"/></binding.soap>
            2. When iterating through the EXCHANGE-scoped Context properties, look for property.hasLabel(SOAPComposition.SOAP_MESSAGE_HEADER).

            The property values will now be the original SOAP Header Elements typed as actual DOM Elements.

            Have fun!

            Show
            David Ward added a comment - - edited SWITCHYARD-710 has been pushed. Now: 1. Set the soapHeadersType: <binding.soap><contextMapper includes=".*" soapHeadersType="DOM"/></binding.soap> 2. When iterating through the EXCHANGE-scoped Context properties, look for property.hasLabel(SOAPComposition.SOAP_MESSAGE_HEADER). The property values will now be the original SOAP Header Elements typed as actual DOM Elements. Have fun!
            Hide
            Gary Brown added a comment -

            Riftsaw and riftsaw-ode pull requests have been applied, but will need to wait for next release before available for switchyard.

            Show
            Gary Brown added a comment - Riftsaw and riftsaw-ode pull requests have been applied, but will need to wait for next release before available for switchyard.
            Hide
            Keith Babo added a comment -

            Pushed.

            Show
            Keith Babo added a comment - Pushed.
            Keith Babo made changes -
            Status Pull Request Sent [ 10011 ] Resolved [ 5 ]
            Resolution Done [ 1 ]

              People

              • Assignee:
                Ivo Bek
                Reporter:
                Gary Brown
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development