Aaron,
Thanks a lot for your help. I will follow your tip and will notch the logging level up to DEBUG ;) However, as far as I know (I've read this somewhere but I can't recall where), when you specify multiple recipients following the syntax you specified (multiple <to> elements or <multicast>), what happens is that the same initial message gets routed to all the recipients. What I want to achieve is a "sequence of invocations", where each recipient gets the result of the processing done by the previous one. Perhaps someone could shed some light on this?? Thanks a lotª Aaron Crickenberger wrote: > > > On Mar 27, 2008, at 1:32 PM, raulvk wrote: > >> However, I have noticed that the Pipeline pattern is only available >> from >> Java DSL, as the element is not defined in the Camel XSD located at: >> http://activemq.apache.org/camel/schema/spring/camel-spring.xsd. > > As I understand it, pipelines are implicitly created when specifying > routes via XML. The following should be equivalent to the example > found at http://activemq.apache.org/camel/pipes-and-filters.html > > <route> > <from uri="direct:a"/> > <to uri="direct:x"/> > <to uri="direct:y"/> > <to uri="direct:z"/> > <to uri="mock:result"/> > </route> > > You have to explicitly specify multicast if this isn't the behavior > you want. I think it would look like this? > <route> > <from uri="direct:a"/> > <multicast> > <to uri="direct:x"/> > <to uri="direct:y"/> > <to uri="direct:z"/> > <to uri="mock:result"/> > </multicast> > </route> > > If you turn on DEBUG level logging when running Camel's unit tests or > examples, you'll see a lot of information about what routing > constructs are used under the hood. > > Hope this helps! > > - aaron > > -- View this message in context: http://www.nabble.com/Camel-Pipeline-not-available-from-XML--tp16329178s22882p16337196.html Sent from the Camel - Users mailing list archive at Nabble.com.
