On Tue, Jul 26, 2011 at 4:06 PM, cwhistler wrote:
> FYI the answer to this issue is the same as the problem I had yesterday, I
> simply needed to close my BufferedReader at the end of the process!
>
Thanks for reporting back. I had a look in the source, and Camel ought
to react accordingly and be
FYI the answer to this issue is the same as the problem I had yesterday, I
simply needed to close my BufferedReader at the end of the process!
--
View this message in context:
http://camel.465427.n5.nabble.com/file-move-option-not-working-when-using-split-tp4616425p4634904.html
Sent from the Came
Hi
I have logged a ticket to improved this in Camel
https://issues.apache.org/jira/browse/CAMEL-4270
On Thu, Jul 21, 2011 at 1:53 PM, cwhistler wrote:
> Do you mean to propagate the entire inbound message into the outbound List so
> that it is available when this List is returned?
>
> pu
Do you mean to propagate the entire inbound message into the outbound List so
that it is available when this List is returned?
public List splitBody(Exchange exchange)
{
String fileName = (String)
exchange.getIn().getHeader(Exchange.FILE_NAME_ONLY);
Hi
You may have a corner case when you decide the return Message
instances in the split bean.
Could you ensure all headers is propagated from the Exchange IN
message in all the returned Message's in that list?
On Wed, Jul 20, 2011 at 6:17 PM, cwhistler wrote:
> I am using camel version 2.7.2
>
