Uploaded image for project: 'ServiceMix Components'
  1. ServiceMix Components
  2. SMXCOMP-629

Refactor component so the Camel route no longer directly accesses the JBI MessageExchange/NormalizedMessage

    XMLWordPrintableJSON

    Details

      Description

      Currently, the servicemix-camel component implements its own Camel Exchange/Message implementations that wrap a JBI MessageExchange/NormalizedMessage, updating the underlying JBI classes on the fly as the Camel route is being executed. This pattern has proven to cause some unwanted side effects (e.g. SMXCOMP-567, SMXCOMP-495).

      Refactoring the component to use the standard Camel Exchange/MEssage implementations and only touch the JBI classes in the endpoints/bindings would solve these issues. Willem already provided a patch for SMXCOMP-563 (upgrade to Camel 2.0) which includes this refactoring.

        Attachments

          Activity

            People

            • Assignee:
              gertvanthienen Gert Vanthienen
              Reporter:
              gertvanthienen Gert Vanthienen
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: