Re: HttpProducer endpoint with unlimited/limited redelivery - memory leak

2014-12-09 Thread Radek Kraus
Hi Willem and Claus, many thank you for fix and JIRA issue too. I felt that one possibility, was to don't register synchronization at all (like was in version 2.12.2), but I wasn't sure with this option (mainly in context of CAMEL-7055). -- View this message in context:

HttpProducer endpoint with unlimited/limited redelivery - memory leak

2014-12-08 Thread Radek Kraus
for any feedback. Radek Kraus. -- View this message in context: http://camel.465427.n5.nabble.com/HttpProducer-endpoint-with-unlimited-limited-redelivery-memory-leak-tp5760285.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Bean component/Bean Binding: Body as InputStream parametr (specified as ${body} in route)

2013-10-02 Thread Radek Kraus
Yes, I know it. It is enough to use second variant (the commented one) of bean component binding. I have already used it. I want only to know if using of simple language (${body}) is a problem, which should be fixed. I will create the JIRA ticket, how Claus suggested. Thanks all for help. --

Re: Bean component/Bean Binding: Body as InputStream parametr (specified as ${body} in route)

2013-10-02 Thread Radek Kraus
The JIRA issue was create https://issues.apache.org/jira/browse/CAMEL-6810. Thanks for help. -- View this message in context: http://camel.465427.n5.nabble.com/Bean-component-Bean-Binding-Body-as-InputStream-parametr-specified-as-body-in-route-tp5740656p5740741.html Sent from the Camel - Users