On Mon, Sep 24, 2012 at 10:46 AM, zuff <bhtan1...@live.com> wrote:
> Hi Claus,
>
> Thanks. That resolved my problem. I didn't even try such a simple
> changes, as I thought I had to introduce the camel FactoryBean into my POJO.
>
>
> I have another issue:
> Even though I found some similar post regarding storing of variable for
> later usage, but most of them are in java DSL which I didnt managed to apply
> directly.
>
What do you want to store?
You can store variables on headers of the message or properties on the exchange.
And the XML DSL has constructs to leverage both kinds.
> <route>
> <from uri="direct:processResult"/>
> <bean ref="convertor"/>
> <bean ref="strategyManager" method="isStrategyCompleted"/>
> <when>
> <simple>${body}</simple>
>
> <bean ref="messageSender" />
> </when>
> <otherwise>
> ....
> </otherwise>
> </route>
>
>
> Will appreciated any advise.
>
> Best Regards,
> Zuff
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Correct-use-of-camelproxy-tp5719716p5719834.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
