ords, then that would be faster
in a single threaded.
> Thanks & regards,
> Ebe
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4955063.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
and publish it
to MQ.
I currently see that it takes little less than a second to process a file of
2000 records.
Thanks & regards,
Ebe
--
View this message in context:
http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4955063.html
Sent from the Camel - Users mailing list archiv
Setting bean invocation result on the IN message:
> 2011-10-31 13:42:43,905 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message:
> 2011-10-31 13:42:43,905 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on t
liter-in-Camel-tp4940967p4953111.html
Sent from the Camel - Users mailing list archive at Nabble.com.
own this )
Camel in Action book chapter 8 and 10 covers this in much more details.
> Please provide some insight into this.
>
> Thanks & regards,
> Ebe
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4940967.html
>
().setBody(builder.toString());
return exchange1;
}
--
View this message in context:
http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4946971.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
.class));
exchange1.getIn().setBody(builder.toString());
return exchange1;
}
--
View this message in context:
http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4946971.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.executorService(threadPool1).to("jms:queue:test_request_3").end()
>.log("Sent all messages to queue");
>
>
> The AggregationStratery does the below concatination.
>
> exchange1.getIn().setBody(exchange1.getIn().getBody(String.class)+exchange2.ge
e1.getIn().setBody(exchange1.getIn().getBody(String.class)+exchange2.getIn().getBody(String.class));
--
View this message in context:
http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4942950.html
Sent from the Camel - Users mailing list archive at Nabble.com.
e are looking into
optimize XPath as well if that is possible.
> Please provide some insight into this.
>
> Thanks & regards,
> Ebe
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4940967.html
> Sent from the Camel
where before it sends them
> to the processer. How does Camel splitter internally work.
>
> I want to make sure that the Splitter does not eat up the memory.
>
> Please provide some insight into this.
>
> Thanks & regards,
> Ebe
>
> --
> View this message i
Splitter does not eat up the memory.
Please provide some insight into this.
Thanks & regards,
Ebe
--
View this message in context:
http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4940967.html
Sent from the Camel - Users mailing list archive at Nabble.com.
12 matches
Mail list logo