camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian de Beer <...@zenaptix.com>
Subject Re: Contributing Scomp Component (was Contributing Stomp Component)
Date Wed, 06 Feb 2013 22:42:36 GMT
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 contribution simillar to ActiveMQ-Camel, but being outside of ASF and Fuse, I
am not privy to any plans for Apollo. 
I have merged the Scomp code with the original Scomp project in Github. I also raised a Sonatype
Jira request to have the Scomp jars made available in the public repo. I shall do the same
for the Camel component, so if you want reference it in your component page, you are welcome.

Kind regards
Ian

Sent from my iPad

On 06 Feb 2013, at 23:50, Christian Müller <christian.mueller@gmail.com> wrote:

> 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 AM, iandebeer <ian@zenaptix.com> wrote:
> 
>> Hi
>> I have created a pull request for Scomp that contains all the
>> modifications I made to that project. I have discussed this with Dejan
>> Bosanac and I am waiting for the pull request to be incorporated. One small
>> snag is that the the test uses an imbedded Apollo broker and because of the
>> Scala 2.10 dependency we now need the latest SNAPSHOT release of Apollo to
>> run the tests. I hope that a Scala 2.10 compliant release of Apollo is
>> planned for the near future.
>> I have moved the camel-scomp component into a a new camel-scomp repo:
>> https://github.com/zenaptix/camel-scomp.git with all the refactorings you
>> suggested.
>> (I am actually happy for the name change, due to this unfortunate
>> ambiguity: http://www.urbandictionary.com/define.php?term=camel%20stomp)
>> So once we have Scomp updated we are good to go.
>> Regards
>> Ian
>> 
>> 
>> On 01 Feb 2013, at 9:09 AM, hekonsek [via Camel] <
>> ml-node+s465427n5726700h93@n5.nabble.com> wrote:
>> 
>>>> That is a good approach.
>>>> ..
>>>> I am waiting for a response.
>>> 
>>> Great :) Just keep me in the loop.
>>> 
>>> --
>>> Henryk Konsek
>>> http://henryk-konsek.blogspot.com
>>> 
>>> 
>>> If you reply to this email, your message will be added to the discussion
>> below:
>>> 
>> http://camel.465427.n5.nabble.com/Contributing-Apollo-Component-tp5726153p5726700.html
>>> To unsubscribe from Contributing Apollo Component, click here.
>>> NAML
>> 
>> 
>> 
>> 
>> 
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Re-Contributing-Scomp-Component-was-Contributing-Stomp-Component-tp5726868.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
> 
> 
> 
> 
> --

Mime
View raw message