Refactor component so the Camel route no longer directly accesses the JBI
MessageExchange/NormalizedMessage
-----------------------------------------------------------------------------------------------------------
Key: SMXCOMP-629
URL: https://issues.apache.org/activemq/browse/SMXCOMP-629
Project: ServiceMix Components
Issue Type: Improvement
Components: servicemix-camel
Affects Versions: servicemix-camel-2009.01
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: servicemix-camel-2009.02
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
