You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Kevin kalmbach (JIRA)" <ji...@apache.org> on 2008/02/07 18:12:35 UTC

[jira] Updated: (SM-1219) camel pipeline does not copy over properties

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

Kevin kalmbach updated SM-1219:
-------------------------------

    Attachment: ToJbiProcessor.java.diff

I think I have a fix to this problem (It may not be the best fix, but it seems to work).

In toJbiProcessor.java, once the jbi processor is finished, only the out content is copied form the jbi exchange back to the camel exchange.

Here is a quick diff that I made that now also copies the properties from the messageExchange's out to the camel's out exchange..

This change also copies the properties from the exchange itself to the camelExchange.

> camel pipeline does not copy over properties
> --------------------------------------------
>
>                 Key: SM-1219
>                 URL: https://issues.apache.org/activemq/browse/SM-1219
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-camel
>    Affects Versions: 3.2.1
>         Environment: Windows/sm 3.2.1
>            Reporter: Kevin kalmbach
>            Priority: Minor
>         Attachments: ToJbiProcessor.java.diff
>
>
> I created a camel pipeline using the following command in MyRouteBuilder.java
>            
> from("jbi:service:.....pipeline")
>                .pipeline("jbi:endpoint:....endpoint1",
>                    "jbi:endpoint:...endpoint2",
>                    "jbi:endpoint:..endpoint3"
>                 );
>           }
> In my first endpoint, I set several Properties (I set the same property several places: exchange.getProperty, exchange.getMessage("in").setProperty and exchange.getMessage("out").setProperty).
> None of these properties gets propagated to the next steps in the pipeline.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.