Ad 1) This is possible today with the consumer.bridgeErrorHandler option. See more details at the file component page http://camel.apache.org/file2
On Mon, Mar 25, 2013 at 3:26 AM, koseki nonuyuki <koseki.nobuy...@gmail.com> wrote: > Hi > > I have some ideas I want to see in Camel 3.0 > > 1)Batched Transaction > As discussed in [1], I'm glad to see this feature in Camel 3.0 or 2.X, if > possible. > When we have to deal with a huge number of data without losing any data, > batched transaction mechanism or similar feature is required. > > 2)Introduce 'Timer + Consumer' instead of PollingConsumer > When we define a route that contains pollingConsumer, such as File consumer, > we have to define two exception logic, one is onException and the other is > component specific error handling. > > How about the idea that we divide pollingConsumer into two part, timer part > and consumer part. > > If the timer component instantiate the Exchange periodically, then next > consumer can handle errors by onException logic, that means we can handle > all errors by onException logic, not using component specific error > handling. > > 3)Print route information when error occured > Like printStackTrace() in Java, Camel can print routeTrace(), that make us > much easier to trace route when we encounter exception. > > > [1] > http://camel.465427.n5.nabble.com/SJMS-and-batched-transactions-td5716910.html > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/DISCUSS-another-camel-3-0-ideas-tp5729737.html > Sent from the Camel Development 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
