Hi Yeah sure we love contributions, so you are welcome to log a JIRA and do a PR or attach a .patch file. http://camel.apache.org/contributing.html
The code should be against master branch so its included in the next release. Then depending on ease we sometimes backport to older releases. On Tue, Sep 9, 2014 at 11:34 AM, Juan José Vázquez Delgado <jvazq...@tecsisa.com> wrote: > Hi all, > > We've recently had to adapt the camel-hazelcast component in order to get > support for distributed topics [1]. We missed this feature in the current > implementation and it was important for us as we need publish-subscribe > semantics according to our product architecture. The source code can be > found here [2]. > > We were planning to raise a Jira ticket to address this but we were not > sure about which fix version parameter would be proper to set. Of course, > we'd propose a proper pull request. > > Please, let me know if this is the right procedure. > > Thanks in advance, > > Juanjo. > > [1] http://hazelcast.org/use-cases/messaging/ > [2] > https://github.com/Tecsisa/camel/tree/master/components/camel-hazelcast/src/main/java/org/apache/camel/component/hazelcast/topic > > -- > > Juan José Vázquez Delgado > > CTO > > Tecsisa > > C/Quintanavides, 19 > > Parque Vía Norte > > Edificio 4, Planta Baja, Oficina A > > 28050 Madrid > > T: +34 91 182 04 70 > > F: +34 91 447 05 11 > > E: jvazq...@tecsisa.com > > W: www.tecsisa.com -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
