On Thu, Apr 26, 2012 at 6:21 AM, Hynek Cihlar <[email protected]> wrote: > > Hynek Cihlar wrote >> >> >> Claus Ibsen-2 wrote >>> >>> On Tue, Apr 24, 2012 at 6:03 PM, Hynek Cihlar <hynek.cihlar@> >>> wrote: >>>> Hello all, >>>> >>>> what would be the best approach to solve the "transform and multiply" >>>> behavior? That is, a message retrieved from an endpoint is transformed, >>>> multiplied and sent down the route pipeline. >>>> >>> >>> What do you mean by multiplied? Do you mean the multicast EIP? >>> http://camel.apache.org/multicast.html >>> >> >> Claus, thank you for your response. >> >> The multicast pattern in this case is not a valid option. The message must >> be transformed in a loop as shows the following pseudo code. >> >> * message is retrieved from the uplink processor >> * message is xpath-queried for a list of values >> * for each value queried above >> * the message is transformed with the current item from the queried list >> * message is sent down the pipeline >> > > Or is this something that cannot be solved with Camel easily? >
If you have complicated control structures then its often easier to just use a java bean for this logic. And then send messages to Camel endpoint from the bean. Or use a dynamic router as the bean if that is feasible > Hynek > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Transform-and-multiply-tp5662517p5666687.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
