On Tue, Jun 16, 2009 at 2:58 PM, huntc<hu...@mac.com> wrote: > > Yes, it looks as though it is the stream cache, but what's interesting is > that you can't disable the stream cache if you're using the default error > handler: > > http://www.nabble.com/Re%3A-StreamCaching-in-Camel-1.6-to22305858.html > > So you've effectively got to disable the error handler for a route if you > don't want to use the stream cache. > > This seems kind of awkward... does Camel 2.0 improve this situation? Yes we will disable StreamCache by default in Camel 2.0 and add a option to enable it per route. Then if people uses stream then they can enable the cache on demand in case they want to let Camel be able to error handling with redeliveris (as it need to read the stream more than once) or content based routing where you also need to read the content.
> -- > View this message in context: > http://www.nabble.com/Avoiding-type-conversions-with-the-direct-component-tp24053271p24053805.html > Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
