[
https://issues.apache.org/activemq/browse/SMXCOMP-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54073#action_54073
]
Gert Vanthienen commented on SMXCOMP-631:
-----------------------------------------
Lars,
The goal is to avoid putting the burden on the users for deciding when to
convert from StreamSource to something else. A Camel route generally needs a
re-readable source type and when you use it inside ServiceMix, the kind of
Source type sent depends on the source component and the log level. The goal
here is to convert to a re-readable type automatically as soon as the Message
reaches the Camel endpoint, so users are not running into any unpleasant
surprises when they turn off debug logging and they suddenly start running into
problems.
The {{preserveStreams}} flag would be for the advanced user, who does
understand the consequences of sending stream-based message into the Camel
router and knows how to deal with those things inside Camel. It's kind of the
other way around of what we're doing right now and it should avoid newbie users
running into stream-handling issues.
Gert
> 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.
