Yep I'd like something like an open LeaderElection API a user can
implement from scratch (i.e. one may want to gahve multipel eladers)
or you can define just the leadership part and the default
implementation does everything else for you.
---
Luca Burgazzoli
On Thu, Sep 15, 2016 at 8:34 AM, Andr
Maybe we can also give the possibility to end user to implement their own
leader election policy.
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On
On Thu, Sep 15, 2016 at 8:14 AM, Luca Burgazzoli wrote:
> Hello everyone,
>
> I've been working on some master/slave RoutePolicy and I'm wondering
> if we can have a proper LeaderPolicy with a standardized
> implementation in Camel 3.0 so one has only to notify when a
> leadership is taken
>
> In
On Wed, Sep 14, 2016 at 3:32 PM, Nicola Ferraro wrote:
> Well, it was one of the drawbacks of the approach. Forcing users to include
> *only* the camel BOM allows us to completely control the dependencies, but
> it's probably a too strict requirement for users.
>
> We can also provide a option 1+2
+1
---
Luca Burgazzoli
On Thu, Sep 15, 2016 at 8:03 AM, Andrea Cosentino
wrote:
> +1, Thanks a lot Gregor!
> --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: ancosen1...@yahoo.com
> Twitter: @os
Hello everyone,
I've been working on some master/slave RoutePolicy and I'm wondering
if we can have a proper LeaderPolicy with a standardized
implementation in Camel 3.0 so one has only to notify when a
leadership is taken
In addition it may be nice to have:
- a support for Leader election from t
+1, Thanks a lot Gregor!
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesday, September 14, 2016 8:36 PM, Gregor Zurowski
wrote:
Hi Everyon
Hi
I have granted you karma to be able to edit.
Thanks for helping the project.
Mind that the documentation is being moved to adoc so you may also
consider updating the docs in the adoc files if its related to Camel
components / languages / data formats etc.
http://camel.apache.org/contributing.
+1
On Wed, Sep 14, 2016 at 8:35 PM, Gregor Zurowski
wrote:
> Hi Everyone:
>
> As previously discussed on the list, we should get a final Camel
> 2.16.4 release out the door. If everyone agrees, I will create a
> release candidate this week. What do you think?
>
> Thanks,
> Gregor
--
Claus
Hello,
this is my branch https://github.com/Fabryprog/camel/tree/CAMEL-10307
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-docker-upgrade-library-test-failure-tp5787511p5787552.html
Sent from the Camel Development mailing list archive at Nabble.com.
LS,
Can you please provide me access to the Camel wiki to I can help improve
the docs.
I have an approved ASF as alvinkwe...@gmail.com.
Thanks in advance.
Kind regards,
Alvin Kwekel
Github user kiransg closed the pull request at:
https://github.com/apache/camel/pull/1173
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user kiransg closed the pull request at:
https://github.com/apache/camel/pull/1176
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
The Apache Jenkins build system has built Camel.trunk.notest (build #2874)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2874/
to view the results.
Hi Everyone:
As previously discussed on the list, we should get a final Camel
2.16.4 release out the door. If everyone agrees, I will create a
release candidate this week. What do you think?
Thanks,
Gregor
I noticed the WMQ_ headers which many times indicate talking to a legacy
WMQ client (non JMS). You may need to set the destination configuration
option for targetClient=0.
Syntax example:
|...|
|.setHeader("CamelJmsDestinationName",
constant("queue:||///MY_QUEUE?targetClient=1"))|
|.to("wmq:
GitHub user Fabryprog opened a pull request:
https://github.com/apache/camel/pull/1177
Camel 10319
https://issues.apache.org/jira/browse/CAMEL-10319
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Fabryprog/camel CAMEL-10319
Alte
Github user tkopczynski closed the pull request at:
https://github.com/apache/camel/pull/1175
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user tkopczynski closed the pull request at:
https://github.com/apache/camel/pull/1174
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Well, it was one of the drawbacks of the approach. Forcing users to include
*only* the camel BOM allows us to completely control the dependencies, but
it's probably a too strict requirement for users.
We can also provide a option 1+2: i.e. a auto-generated Camel BOM without
any conflict with the s
GitHub user kiransg opened a pull request:
https://github.com/apache/camel/pull/1176
CAMEL-10317: Added support to use Http synchronous client with Olingoâ¦
â¦2 Component
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Infosys/c
Hi,
I helped create the original implementation. Is the code you are working on
in a branch that I might be able to access so I can take a look?
Thanks,
Andy
On Tue, Sep 13, 2016 at 9:10 AM, fabryprog
wrote:
> This is maven dependency tree
>
>
> OpenJDK 64-Bit Server VM warning: ignoring opti
Hi Nicola
Great work on all this Spring Boot starter stuff.
I would like to discuss/hear more about the #1 option you listed on
https://github.com/apache/camel/pull/1164
I think that end users would really prefer their Spring Boot
applications to be "pure" spring boot by having the Spring Boot B
The JMSMessageID cannot be set by a client, its generated by the JMS
client/broker.
And typically for the JMSCorrelationID you would use a String type.
The JMS spec do not allow using byte arrays in JMS headers.
https://docs.oracle.com/javaee/7/api/javax/jms/Message.html
On Tue, Sep 13, 2016 a
24 matches
Mail list logo
