Hi ,
I need our camel route, which is being initialized using configurations
stored in database, to re-initialize on every change in database
configuration at run time(Without restarting server)?
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/RE-Re-Intializing-Ca
+1 (binding)
Thanks Gregor!
Babak
> On 14 May 2017, at 12:01, Gregor Zurowski wrote:
>
> Hi Everyone:
>
> This is a vote for releasing Apache Camel 2.17.7, a new patch release
> that includes 15 bugfixes and improvements. This will likely be our
> last official patch release for the 2.17.x b
Hi Luca,
On Tue, May 16, 2017 at 6:23 PM, Luca Burgazzoli wrote:
> What would be the best option to keep the auto generation awesomeness
> and at the same time have a way to tweak the process ?
BeanDefinitionRegistryPostProcessor can remove and add bean
definitions, so you can do pretty much any
The Apache Jenkins build system has built Camel.2.19.x.notest (build #12)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/12/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3213)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3213/
to view the results.
GitHub user dmvolod opened a pull request:
https://github.com/apache/camel/pull/1699
CAMEL-11288: camel-grpc producer incorrectly called async services
The unit-tests are also completely rewritten
You can merge this pull request into a Git repository by running:
$ git pull http
+1 (binding)
---
Luca Burgazzoli
On Tue, May 16, 2017 at 11:19 AM, Claus Ibsen wrote:
> +1 (binding)
>
> On Sun, May 14, 2017 at 12:01 PM, Gregor Zurowski
> wrote:
>> Hi Everyone:
>>
>> This is a vote for releasing Apache Camel 2.17.7, a new patch release
>> that includes 15 bugfixes and impro
Hello,
as today the camel-package-maven-plugin is responsible to generate
component starters so it generates the properties configuration class
as well of the auto configuration one which is good but there may be
some cases in which one may want to further tweak the bean creation
process, i.e. for
The Apache Jenkins build system has built Camel.2.19.x.notest (build #11)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/11/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3212)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3212/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3211)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3211/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3210)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3210/
to view the results.
Hi
See ticket
https://issues.apache.org/jira/browse/CAMEL-11215
I pushed a potential fix/improvement to the branch
https://github.com/apache/camel/tree/CAMEL-11215
A new option has been introduced, breakOnFirstError (yeah naming is
hard) that you can set to true, so the consumer will then stop
c
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1693
---
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 enab
Hi
Cannot reproduce this problem
https://github.com/apache/camel/commit/c60691dbb1066778d1cc86c44c4e2db1319e4566
On Mon, May 15, 2017 at 12:49 PM, Claus Ibsen wrote:
> Hi
>
> Can you log a JIRA ticket
> http://camel.apache.org/support.html
>
> On Fri, May 12, 2017 at 5:38 PM, mbenmbouh wrote:
>
Hi,
The Camel community had a call for the design of a new logo[1] and we
put up the design proposals for a community vote[2].
We would like to thank everyone for participating either by submitting
their logo design proposal, commenting and collaborating with the
authors or casting the vote. Stay
Github user prashant2402 closed the pull request at:
https://github.com/apache/camel/pull/1697
---
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 i
Github user guyv closed the pull request at:
https://github.com/apache/camel/pull/1698
---
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 enable
+1 (binding)
On Sun, May 14, 2017 at 12:01 PM, Gregor Zurowski
wrote:
> Hi Everyone:
>
> This is a vote for releasing Apache Camel 2.17.7, a new patch release
> that includes 15 bugfixes and improvements. This will likely be our
> last official patch release for the 2.17.x branch
> (https://git-
The Apache Jenkins build system has built Camel.2.19.x.notest (build #9)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/9/ to
view the results.
+1 (binding).
Thanks Gregor
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Sunday, May 14, 2017 12:02 PM, Gregor Zurowski
wrote:
Hi Everyone
21 matches
Mail list logo
