Uploaded image for project: 'SwitchYard'
  1. SwitchYard
  2. SWITCHYARD-2920

Tests with SwitchYardRunner do not call CXF Interceptors of SOAP Service Binding

    Details

    • Steps to Reproduce:
      Hide

      I've attached a reproducer, which is a minor enhancement of a switchyard quickstart demo project.
      There is only one test class (WebServiceTest), which looks for a HTTP header. This header should be set in the CXF Interceptor, which is unfortunately not called.
      The CXF Interceptor is attached to the SOAP binding in the switchyard.xml and the context mapper also includes everything, so that no header is removed.

      Show
      I've attached a reproducer, which is a minor enhancement of a switchyard quickstart demo project. There is only one test class (WebServiceTest), which looks for a HTTP header. This header should be set in the CXF Interceptor, which is unfortunately not called. The CXF Interceptor is attached to the SOAP binding in the switchyard.xml and the context mapper also includes everything, so that no header is removed.
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      There is a partial workaround, which does not meet typical customer needs.
      1. <soap:inInterceptors> does not work with SwitchyardRunner, unfortunately. At this moment, you need to use cxf.xml to define in/out interceptors for SOAP binding endpoints.
      2. Even in cxf.xml, somehow cannot be set up on a per endpoint basis. The attached example uses <cxf:bus> instead, which means the interceptor configurations affect all SOAP endpoints in the single SwitchYard application.

      Show
      There is a partial workaround, which does not meet typical customer needs. 1. <soap:inInterceptors> does not work with SwitchyardRunner, unfortunately. At this moment, you need to use cxf.xml to define in/out interceptors for SOAP binding endpoints. 2. Even in cxf.xml, somehow cannot be set up on a per endpoint basis. The attached example uses <cxf:bus> instead, which means the interceptor configurations affect all SOAP endpoints in the single SwitchYard application.

      Description

      We want to test this functionality by using the SwitchYardRunner and HTTPMixIn test support (as described e.g. in https://docs.jboss.org/author/display/SWITCHYARD/Testing).
      Unfortunately the CXF Interceptors of the tested composites are not called and therefore the tests are useless.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  igarashitm tomohisa igarashi
                  Reporter:
                  david.boeren David Boeren
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: