[jira] Resolved: (SMXCOMP-629) Refactor component so the Camel route no longer directly accesses the JBI MessageExchange/NormalizedMessage

["Gert Vanthienen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/SMXCOMP-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gert Vanthienen resolved SMXCOMP-629.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.4

Fix committed in http://svn.apache.org/viewvc?view=rev&revision=811310 for trunk
and backported to the 3.2.x branch in http://svn.apache.org/viewvc?view=rev&revision=811338

Because the refactoring had to be backported to ServiceMix 3.2.x, I left the JbiExchange/JbiMessage classes in to ensure compatibility, but they have been marked deprecated and the plan is to remove them entirely from trunk as part of the upgrade to Camel 2.0 (SMXCOMP-563).

These commits also include the unit tests provided by Willem for SMXCOMP-626 and by Hans for SMXCOMP-17 -- both issues have been addressed as part of the refactoring.  Thanks to both Willem and Hans for providing those patches!

And another thanks to Willem who provided the ideas for this refactoring as part of his patch to upgrade to Camel 2.0 (cfr. SMXCOMP-563)!

> 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: 3.2.4, 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.