But if I do filter on the pipeline it'll determine whether the entire pipeline is or isn't performed, right? So to break out of the pipeline I'd have to put the filter on each pipelined item, such as
from X filter when Y to A filter when Y to B end // filter to C // do something after filter for all messages so as to pick up when Y became false. Since I use an instance of Pipeline with an ArrayList of Processors, this would become an ArrayList of FilterProcessor(predicate, processor)? On Wed, Apr 20, 2011 at 4:59 AM, Claus Ibsen <[email protected]> wrote: > On Wed, Apr 20, 2011 at 12:42 AM, Donald Whytock <[email protected]> wrote: >> I ask because it appears to, in my application where I'm using >> ROUTE_STOP to break out of a pipeline. >> >> Perhaps there should be some mechanism for breaking out of a pipeline >> without killing the whole route? A PIPELINE_STOP property, or maybe >> ROUTE_STOP could contain the ID of the route to be broken out of, >> allowing containing routes to continue? >> > > You can use the filter EIP to only process messages based on a predicate. > > from X > filter when Y > to A > to B > end // filter > to C // do something after filter for all messages > >> >> On Tue, Apr 19, 2011 at 3:40 PM, Donald Whytock <[email protected]> wrote: >>> Hi all... >>> >>> Does using ROUTE_STOP on an email exchange prevent the message from >>> being deleted from the POP3 server? >>> >>> Don >>> >> > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: [email protected] > Web: http://fusesource.com > CamelOne 2011: http://fusesource.com/camelone2011/ > Twitter: davsclaus > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ >
