[
https://issues.apache.org/activemq/browse/SMXCOMP-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54070#action_54070
]
Lars Heinemann commented on SMXCOMP-631:
----------------------------------------
I think it's maybe the best to make the StreamDataSource itself re-readable by
default. When browsing the forum there often problems arise regarding
StreamSource and re-readability. Wdyt?
> Automatically convert StreamSource into a re-readable type and allow user to
> force usage of streams
> ---------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-631
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-631
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.02
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-camel-2009.02
>
>
> For Camel 2.0, stream caching is no longer enabled by default. However, when
> using Camel inside ServiceMix, most of the times the data has to be in a
> re-readable format (content-based routing, multicasts, deadletter channel
> error handling, ...). In order to avoid that the users would have to enable
> stream caching on every Camel route inside ServiceMix, it would be better if
> we would convert our data into a re-readable type by default and allow the
> user to override that behavior by adding a flag to the uri.
> An example:
> {code}
> from("jbi:name:my-endpoint").to...
> -> would send a re-readable source type
> from("jbi:name:my-endpoint?preserveStreams=true").to...
> -> would preserve the incoming message's type, even if it's a
> Stream/StAXSource
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
