I still have some things to clean up and a few more tests to write but I'd
like to start getting some comments:
https://github.com/brreitme/camel/commit/b77e1297f2f8371257a36e56c9cfd096720c39ca
--
View this message in context:
http://camel.465427.n5.nabble.com/Adding-inOut-support-to-the-Rabbi
I just typed a wrong command when doing the release and need to do the release
again.
Please don’t commit any code to Camel-2.15.x branch in the next 4 hours.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese
The Apache Jenkins build system has built Camel.2.14.x.notest (build #149)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.14.x.notest/149/
to view the results.
Hi Christian,
I had similar issues when building camel-cassandra on a Linux box with
Java 7. Cassandra spawns a huge amount of threads when running the
component's unit tests. The problem was caused by not having enough
file descriptors available to spawn new threads. This eventually led
to the er
Hi,
Regarding 1) - you don't have to know the endpoints upfront because you can
connect resequencer to the Recipient List using the direct endpoint. Just
as Willem demonstrated.
Cheers.
wt., 28.04.2015 o 06:38 użytkownik Sumit
napisał:
> Hi,
>
> Thanks for your quick reply.
>
> We have followi
Hi Pontus,
For now, commit only to Google Code.
Cheers.
wt., 28.04.2015 o 09:05 użytkownik Pontus Ullgren
napisał:
> Pressed send a bit fast there sorry.
>
> I'm planning to have a look at CAMEX-61[1] today and it would be nice to
> know where it should be committed.
>
>
> [1] https://camel-ex
Pressed send a bit fast there sorry.
I'm planning to have a look at CAMEX-61[1] today and it would be nice to
know where it should be committed.
[1] https://camel-extra.atlassian.net/browse/CAMEX-61
On Tue, 28 Apr 2015 at 09:00 Pontus Ullgren wrote:
> Think I already voted in another thread b
