You can use the setExchangePattern before the recipient list to alter it. But yeah maybe we should consider having to override it like you can do on <to> Mind that this override is "local" only, and the MEP is not changed on the original exchange, being routed afterwards.
On Wed, May 23, 2012 at 1:57 PM, Raul Kripalani <[email protected]> wrote: > Hi, > > Was just about to open a JIRA improvement ticket to add the capability to > the recipientList DSL to override the exchange pattern. Following is the > ticket body: > > Right now, the exchanges sent by the recipientList DSL absorb the exchange >> pattern of the incoming exchange. We should add a capability to overwrite >> the exchange pattern. >> > > >> Consider for example a route with a InOut CXF consumer wanting to >> broadcast a message to a number of AMQ queues dynamically computed from a >> header. Right now, the exchanges will be sent with an InOut pattern and >> there is no way to override this behaviour unless we use onPrepareRef. > > > But just wanted to double-check just in case there's a way to achieve this > (other than using onPrepareRef) that I'm unaware of? > > Thanks, > > *Raúl Kripalani* > Principal Consultant | FuseSource Corp. > [email protected] | fusesource.com <http://www.fusesource.com/> > skype: raul.fuse | twitter: @raulvk <http://twitter.com/raulvk>, > @fusenews<http://twitter.com/fusenews> > > <http://twitter.com/fusenews> -- 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/
