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

operationSelector & contextMapper can not be specified together

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 0.6
    • Fix Version/s: 0.7
    • Component/s: common
    • Labels:
      None

      Description

      We would get an following error if operationSelector and contextMapper/messageComposer are specified together

      [ERROR] Failed to execute goal org.switchyard:switchyard-plugin:0.6.0-SNAPSHOT:configure (default) on project switchyard-timer: Model [org.switchyard.config.model.switchyard.v1.V1SwitchYardModel] is invalid: cvc-complex-type.2.4.a: Invalid content was found starting with element 'selector:operationSelector'. One of '{"urn:switchyard-component-camel:config:1.0":messageComposer, "urn:switchyard-component-camel:config:1.0":name}' is expected. -> [Help 1] 
      

      We probably can get around this if the operationSelector definition is moved from component-common to the schema of each bindings like contextMapper/messageComposer, but then, when you add another operationSelector - e.g. operationSelector.rules - we would need to add it to all of those binding schemas.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  igarashitm tomohisa igarashi
                  Reporter:
                  igarashitm tomohisa igarashi
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: