Re: Build on trunk fails @ camel-example-cdi

2012-09-23 Thread Charles Moulliard
Hi Christian, Thx. I will have a look. Regards, Charles On Sat, Sep 22, 2012 at 10:25 PM, Christian Müller < christian.muel...@gmail.com> wrote: > Hi Charles! > > I fixed this with rev 1388892 [1]. Could you please check whether this fix > looks good for you. > > [1] > http://svn.apache.org/vi

Re: Apache Extras notifications (was: Disable GitHub commenting [httpd])

2012-09-23 Thread Greg Stein
On Sep 23, 2012 11:48 PM, "Luciano Resende" wrote: > > On Sun, Sep 23, 2012 at 4:11 PM, Greg Stein wrote: > > Benson, > > > > The license stuff is a red herring. Ignore it. > > > > The primary issue is figuring where the notification emails sent to. > > > > -g > > > > Sorry for jumping on this so

camel-ftp via proxy

2012-09-23 Thread mywish
Hi, I am trying using camel-ftp to route file to ftp server via proxy. But as I know, camel-ftp don't support proxy. FTP4J is not a component of apache camel. So I tried to using a custom ftpClient like this: FTPClient client = new FTPClient(); System.getProperties().put("socksProxyPort", "8089");

Re: Apache Extras notifications (was: Disable GitHub commenting [httpd])

2012-09-23 Thread Luciano Resende
On Sun, Sep 23, 2012 at 4:11 PM, Greg Stein wrote: > Benson, > > The license stuff is a red herring. Ignore it. > > The primary issue is figuring where the notification emails sent to. > > -g > Sorry for jumping on this so late, but initially I thought this was just a infra issue and I saw few di

Re: Apache Extras notifications (was: Disable GitHub commenting [httpd])

2012-09-23 Thread Greg Stein
Benson, The license stuff is a red herring. Ignore it. The primary issue is figuring where the notification emails sent to. -g On Sep 23, 2012 6:27 PM, "Benson Margulies" wrote: > With all respect to everyone involved, I really doubt that the infra > list is the best place for the Camel PMC to

Re: Apache Extras notifications (was: Disable GitHub commenting [httpd])

2012-09-23 Thread Benson Margulies
With all respect to everyone involved, I really doubt that the infra list is the best place for the Camel PMC to refine their understanding of how best to cope with glue code for an LGPL dependency. If infra@ feels that fixing the email flow from extras to core lists is inappropriate due to their v

Re: Apache Extras notifications (was: Disable GitHub commenting [httpd])

2012-09-23 Thread Daniel Shahaf
Christian Müller wrote on Sun, Sep 23, 2012 at 19:29:21 +0200: > Sorry for being inaccurate. I didn't understood your response as you mean > it (only after your last mail). I'm not an English native speaker. Please > have understanding for it... > No problem. > We cannot move the camel-extra sou

Re: Apache Extras notifications (was: Disable GitHub commenting [httpd])

2012-09-23 Thread Christian Müller
Sorry for being inaccurate. I didn't understood your response as you mean it (only after your last mail). I'm not an English native speaker. Please have understanding for it... We cannot move the camel-extra sources to Apache hardware because they have dependencies which are not allowed at Apache

[Patch] CAMEL-5643 Allow users to store body and arbitrary headers as text within a datasource

2012-09-23 Thread AlanFoster
Hi, Just letting you know I've added a patch for https://issues.apache.org/jira/browse/CAMEL-5643 I'd appreciate any feedback on it :) Alan -- View this message in context: http://camel.465427.n5.nabble.com/Patch-CAMEL-5643-Allow-users-to-store-body-and-arbitrary-headers-as-text-within-a-dat

Re: Is the SEDA producer really async?

2012-09-23 Thread Babak Vahdat
> Hi fellow riders, > The async routing engine page in the docs [1] suggests that the SEDA > Producer is async. > I may be slightly confused, but I don't see the SedaProducer returning > "false" in its process() method at any point (overridden from > DefaultAsyncProducer). BTW the method is *not

Re: Is the SEDA producer really async?

2012-09-23 Thread Babak Vahdat
Am 23.09.12 13:53 schrieb "Babak Vahdat" unter : >Hi Raul, > >As the documentation states: > > When we say a component is supported, that means the component is >leveraging the asynchronous model. > >And yes the SedaProducer leverages the asynchronous model because it >extends the *abstract* Defa

Re: camel-jaxb failing for me locally...

2012-09-23 Thread James Carman
Thanks! That is a cool feature. Sent from my iPad On Sep 23, 2012, at 5:20 AM, Babak Vahdat wrote: > Hi > > I just fixed it, so do an update on camel-jaxb which should now make the > test pass again. > > BTW this unit-test verifies a new cool feature in Camel 2.11 provided by > Claus Ibsen.

Re: Is the SEDA producer really async?

2012-09-23 Thread Babak Vahdat
Hi Raul, As the documentation states: When we say a component is supported, that means the component is leveraging the asynchronous model. And yes the SedaProducer leverages the asynchronous model because it extends the *abstract* DefaultAsyncProducer base class (abstract because it actually d

Re: camel-jaxb failing for me locally...

2012-09-23 Thread Babak Vahdat
Hi I just fixed it, so do an update on camel-jaxb which should now make the test pass again. BTW this unit-test verifies a new cool feature in Camel 2.11 provided by Claus Ibsen. Thanks! http://camel.465427.n5.nabble.com/CONF-Apache-Camel-gt-JAXB-td5719722.html Babak -- View this message in