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

Add the possibility to define ExchangeInterceptors per wire

    Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: common
    • Labels:
      None

      Description

      Now, when defining an ExchangeInterceptors in a SwitchYard composite it applies to every wire defined in the composite. This is not ideal as usually you add logic to opt if the processor applies to the specific request. Also, you may want to have same type of request applying different ExchangeProcessor, or have mock implementations injected via @Alternatives in JUnit tests.

      ExchangeInterceptors, when defined, could be annotated with the from/to indicate the wire it applies, and should only be injected at deployment time to the appropriate wire. If now, there is a common Processor that executes all defined ExchangeInterceptors, this could be changed to only register the ExchangeInterceptors to the appropriate wire.
      It will improve on:

      • Usability
      • Performance
      • Reusability and applications design

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jorgemoralespou_2 Jorge Morales Pou
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: