[
https://issues.apache.org/activemq/browse/CAMEL-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51196#action_51196
]
Gert Vanthienen commented on CAMEL-1332:
----------------------------------------
Claus, I don't think enabling it at the start of the route is enough. If you
look at CAMEL-1271, the problem there was an InOut style interaction with an
external service in the middle of the route. If the response from the service
is a streaming data type (e.g. a StreamSource), you would need to cache that as
well to ensure proper handling.
> 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.
