[
https://issues.apache.org/activemq/browse/CAMEL-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41702#action_41702
]
James Strachan commented on CAMEL-179:
--------------------------------------
Great stuff. I guess there are more routes that could lead to the same body
being re-read other than just the multicast type; so I guess we might wanna
apply this interceptor by default anyway - or at least make it a default and
let folks remove it maybe?
I can imagine we'd also wanna do things like support other types such as...
* InputStream
* Reader
I wonder if the default behaviour should be to make things re-readable by
default to avoid common issues (e.g. retry logic) - but have some way where we
can explicitly disable the re-reading behaviour when we really don't want it
(which is gonna be pretty rare)
> Handling StreamSource when routing to multiple endpoints
> --------------------------------------------------------
>
> Key: CAMEL-179
> URL: https://issues.apache.org/activemq/browse/CAMEL-179
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.1.0
> Reporter: Gert Vanthienen
> Priority: Minor
> Attachments: CAMEL-179.diff
>
>
> If the original message in the example below contains a StreamSource, the
> second target in the to() will probably fail. Auto-converting it to e.g.
> DOMSource should fix this...
> {code}
> from("jbi:service:urn:servicemix:tutorial:wiretap")
> .to("jbi:endpoint:urn:servicemix:tutorial:jms:myQueue",
> "jbi:endpoint:urn:servicemix:tutorial:file:sender");
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
