[jira] Commented: (CAMEL-1332) StreamCachingInterceptor can be enabled both as a strategy and as an interceptor -- should only be a strategy

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51192#action_51192 ] 

Claus Ibsen commented on CAMEL-1332:
------------------------------------

Gertv I think it should be just as the Tracer, and it should be enabled by default.

For instance if you do transacted routing (eg not using DeadLetterChannel) and content based router where you do xpath predicates then the payload is gonna be read multiple times. And therefore we need the cache to be default enabled.

We can add a easy switch in the Spring XML to disable it for people really not liking it, eg just like the Tracer.

Then we can remove the special code in DeadLetterChannel, Multicast that enables it.

> StreamCachingInterceptor can be enabled both as a strategy and as an interceptor -- should only be a strategy
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1332
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1332
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.5.0
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>             Fix For: 2.0.0, 1.6.1
>
>
> Right now, there are two ways of enabling stream caching:
> - explicitly enable it through the DSL
> - implicitly enable it through e.g. a Multicast or DeadletterChannel
> We should make that a single way of enablement or else document the rationale for the difference properly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.