Re: BeanInfo performance issues

Hi Antoine, Do you mind to submit the patch into the JIRA[1] that Christian just created? When you submit the patch , the default action is grant it with ASF license. In this way we can keep the ball running :) Willem -- View this message in context: http://camel.465427.n5.nabble.com/BeanIn

AW: http://camel.apache.org/bean-binding.html#BeanBinding-Parameterbinding

cool ;) Jan -Ursprüngliche Nachricht- Von: Willem jiang [mailto:willem.ji...@gmail.com] Gesendet: Donnerstag, 7. Februar 2013 02:37 An: dev@camel.apache.org Betreff: Re: http://camel.apache.org/bean-binding.html#BeanBinding-Parameterbinding Hi Jan, Thanks for the pointing that out, it

Camel.trunk.notest - Build # 1786 - Failure

The Apache Jenkins build system has built Camel.trunk.notest (build #1786) Status: Failure Check console output at https://builds.apache.org/job/Camel.trunk.notest/1786/ to view the results.

Re: http://camel.apache.org/bean-binding.html#BeanBinding-Parameterbinding

Hi Jan, Thanks for the pointing that out, it makes document more easy to understand. FYI I just updated the document with your suggestion. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.c

Re: Contributing Scomp Component (was Contributing Stomp Component)

My need for this component arose from wanting to connect to ActiveMQ Apollo from within an Akka actor. Both of these (Akka and Apollo), have no Scala bias and works just fine in Java projects. As I suggested, it would probably be a better fit to provide the component as an Apollo-Camel contribut

Re: [camel-extra] 2.10.1 release

>> For Spring we have a broad version range Issue updated [1]. I'll handle this before the next release. > I'll try to stage the release this week. Camel Extra 2.10.1 release has been staged at Sonatype OSS repository [2]. Peer review of the staged artifacts will be highly appreciated. If everyt

Re: BeanInfo performance issues

I went ahead and opened the issue [1] so we don't forget it. [1] https://issues.apache.org/jira/browse/CAMEL-6043 Best, Christian On Tue, Feb 5, 2013 at 1:17 PM, Claus Ibsen wrote: > On Tue, Feb 5, 2013 at 8:40 AM, Antoine DESSAIGNE > wrote: > > Hi, > > > > I opened nabble and the archive in

Re: Contributing Scomp Component (was Contributing Stomp Component)

Because Camel and Camel-Extra are Java based projects, I don't think we should integrate this component (even if it's a cool component for Scala guys). As Claus mentioned, we can add a link from our components page to your GitHub project, if you want. Best, Christian On Mon, Feb 4, 2013 at 7:14 A

Re: [DISCUSS][CAMEL-3.0] Does camel need a web console

In regards to camelwatch, I am having the same issue as James building camelwatch due to the new dependency on the jmxc library. It seems as though in a recent update, sksamual has added a new dependency on https://github.com/sksamuel/jmxc. When I try to build jmxc library I get some scala

http://camel.apache.org/bean-binding.html#BeanBinding-Parameterbinding

In the examples there is a method public String doSomething(String body) with a String as return type. Directly under that this is written "Or the Exchange example. Notice that the return type must be void when there is only a single parameter:" How does that fit - void return type and String

AW: [DISCUSS] - Moving towards Camel 2.11 release

Maybe a table (feature x option): Feature||| Option | F1 | F2 | description ---+++-- Opt1 | X | - | bla bla Opt2 | O | O | blub blub X - required O - supported - - not supported Jan -Ursprüngliche Nachricht- Von: Bilgin Ibryam [mailto:bibr...@gm

Re: [DISCUSS] - Moving towards Camel 2.11 release

Guys, thanks for fixing the CS and other issues with the Redis component. I didn't mentioned the new component on the release or components page because it doesn't have documentation yet. But I've assigned CAMEL-6001 and will be working on the documentation these days. I'd love to see the new com