Re: Contributing Apollo Component

2013-01-24 Thread Kai Wähner
Ian, just FYI: We had the discussion about Scala components some months ago, when I thought about creating a Neo4j Scala component: http://camel.465427.n5.nabble.com/Create-a-new-Camel-component-via-Scala-Component-Archetype-td5708543.html Claus had some good arguments there not to use Scala. Nev

Re: [CAMEL-3.0] Start moving forward

2013-01-24 Thread Guillaume Nodet
For the webconsole, I'd make sure to have a look at http://hawt.io/ On Wed, Jan 23, 2013 at 11:03 PM, Christian Müller < christian.muel...@gmail.com> wrote: > Lukasz, could you have a look at [1]!? > We are looking for a champion for the task "Light-weight web console" (if > it has enough endors

Re: Contributing Apollo Component

2013-01-24 Thread Claus Ibsen
On Thu, Jan 24, 2013 at 1:20 PM, iandebeer wrote: > Hi > I have developed a Stomp Component for use with Apollo. It supports in, out > and in-out exchange patterns. I assume its a generic stomp component, so you can use it with any stomp compliant brokers, eg also ActiveMQ. eg its not only for Ap

Re: Contributing Apollo Component

2013-01-24 Thread Willem jiang
Hi Ian, I think is not a big deal to host the component in Apollo or Camel. But I'd like to help to review the code, did you have chance to push the code into github? If so, I could spend some time to have a look at the code :) -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat

Re: Contributing Apollo Component

2013-01-24 Thread iandebeer
Hi Christian Unfortunately, I will not be able to find the time to rewrite it Java. A large portion of Apollo is written in Scala. (as is HawtDispatch which is also used in the project). Maybe it would be an option to provide the component from the Apollo side, similar to the ActiveMQ component.

Re: [CAMEL-3.0] Start moving forward

2013-01-24 Thread Hadrian Zbarcea
Anybody. We need to hear the ideas of even non-committers actually. However if there are enough endorsements I'd think there is no need to add another one. What is more important is to see if anybody has anything against an idea and what kind of arguments he'd bring to the table. Hadrian On

Re: Contributing Apollo Component

2013-01-24 Thread Christian Müller
I know, we have a camel-scala component to integrate Scala. This make sense to me. I don't like the idea to add a comonent which is written in Scala to integrate with other protocols like Stomp. Is it possible to (re-) write it in Java? Only a few committer are familiar with Scala and are able to m

Re: [CAMEL-3.0] Start moving forward

2013-01-24 Thread Henryk Konsek
> (if > it has enough endorsements). Talking about endorsements... Can all committers endorse or is this privilege reserved for the PMC masonic lodge? :) -- Henryk Konsek http://henryk-konsek.blogspot.com

Re: Contributing Apollo Component

2013-01-24 Thread Willem jiang
It sounds cool. Please take some time to go through the contributing page[1], you can fill a JIRA and attach your patch into it. [1]http://camel.apache.org/contributing.html -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat

Contributing Apollo Component

2013-01-24 Thread iandebeer
Hi I have developed a Stomp Component for use with Apollo. It supports in, out and in-out exchange patterns. It is written is Scala 2.10 and the Stomp client code was forked from the Scomp project. Is there any interest in this and if so what would be the process to contribute the code. Kind regard

Re: [DISCUSS] - Moving towards Camel 2.11 release

2013-01-24 Thread Babak Vahdat
Am 24.01.13 08:39 schrieb "Claus Ibsen" unter : >On Thu, Jan 24, 2013 at 7:48 AM, Babak Vahdat > wrote: >> +1 to turn off the checkstyle directly inside the code itself and not >>the >> xml. As a concrete example we've got the "maximum 7 ParameterNumber >>rule" >> being commented out since 2008