camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1332) StreamCachingInterceptor can be enabled both as a strategy and as an interceptor -- should only be a strategy
Date Wed, 15 Apr 2009 09:25:31 GMT

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

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

trunk: 765089

There is a issue with TX routes and steam cache I need to sort it. There is a TODO in some
unit tests in camel-spring that shows the problem.
I know what to do but I wanted to get this part with pure stream cache committed before I
mess with TX error handler.

> 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: Claus Ibsen
>             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.


Mime
View raw message