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.
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.