Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-7082

SwitchYard/Camel route loses 'SOAPAction' through Reference

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • jboss-fuse-6.3
    • SwitchYard
    • None
    • % %
    • Hide

      Deploy enclosed Dynamic Web Application via Eclipse (or port the simple artifacts to a Maven project for outside-IDE deployment.)

      Deply and run the SwithYard project. Using a tool like Wireshark, observe the failure of efforts to change the 'SOAPAction' header.

      Show
      Deploy enclosed Dynamic Web Application via Eclipse (or port the simple artifacts to a Maven project for outside-IDE deployment.) Deply and run the SwithYard project. Using a tool like Wireshark, observe the failure of efforts to change the 'SOAPAction' header.

    Description

      A SwitchYard application with a Camel route that directly invokes a SOAP-bound reference fails to propagate 'SOAPAction' to the called web service.

      Snippet, shows the Camel route's use of the Reference:
      <to id="call_WS" uri="switchyard://GreetWebSvc?operationName=greet"/>

      Efforts to set 'SOAPAction' as a header prior to the above invocation fail. (Headers of other names propagate well.)

      Efforts to make a custom ContextMapper for SwitchYard likewise fail (but succeed for headers of other names.)

      Attachments

        Activity

          People

            tcunning@redhat.com Thomas Cunningham
            rhn-support-rick Rick Wagner
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: