Cool, thx.
On Sep 9, 2014 7:57 AM, "Willem Jiang" wrote:
> FYI, I just added a unit test and use FQN to specify the type converter
> name.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twit
Great!. I've provided both a Jira issue [1] and the corresponding Git PR
[2].
Thanks for your help!.
BR,
Juanjo.
[1] https://issues.apache.org/jira/browse/CAMEL-7794
[2] https://github.com/apache/camel/pull/263
2014-09-09 11:41 GMT+02:00 Claus Ibsen :
> Hi
>
> Yeah sure we love contributions,
I'm about to push a change to the MDC UoW, and perhaps another one to the
log endpoint.
Hopefully sometime today ;-)
Regards,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in
GitHub user juanjovazquez opened a pull request:
https://github.com/apache/camel/pull/263
Topics support in camel-hazelcast
As discussed in developer mailing list [1], this PR is intended to add
support for Hazelcast distributed topics in Camel.
[1]
http://camel.465427.n5.
As I need to verify some of service mix bundles (release candidate), I postpone
the Camel release cut to Thursday morning.
Because current camel master are in good sharp of release, please hold your big
changes until we cut the release and make sure your last minute commit doesn’t
break anythin
FYI, I just added a unit test and use FQN to specify the type converter name.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On September 9, 2014 at 6:23:29 PM, Jon
Ah spotted a package name used in camel-core so I switched to that. Will
double check today which one I need to use.
On Sep 9, 2014 3:02 AM, "Claus Ibsen" wrote:
> Hi
>
> In the type converter file you should use the FQN of the class name,
> so the change was in fact not correct.
>
>
> On Tue, Se
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
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 b
