Github user veithen closed the pull request at:
https://github.com/apache/camel/pull/772
---
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
Yeah the documentation is a goal for Camel 3. All the component
documentation will be able in the future to be auto updated and kept
in sync from the source code, based on all the recent work we have
done to annotate and include the docs in the build.
And we would also be able to generate per
Hi
Yeah the other components that can re-connect do it like B. I think we
should refactor the code, which is fine to introduce in Camel 2.17
onwards.
So I suggest to go with B.
On Thu, Jan 14, 2016 at 11:29 PM, unleashed85 wrote:
> I'm working on CAMEL-8742 where RabbitMQ consumers will never
I'm working on CAMEL-8742 where RabbitMQ consumers will never reconnect if
the RabbitMQ channel gets closed.
Its actually really easy to detect when the channel is closed because the
com.rabbitmq.client.Consumer interface has a handleShutdownSignal() method
that will get called. However I would ap
GitHub user yogeshrao opened a pull request:
https://github.com/apache/camel/pull/774
CAMEL-9508 : support jms 2.0 in osgi manifest
added jms version range in pom.xml for osgi manifest
You can merge this pull request into a Git repository by running:
$ git pull https://github.c
Github user yogeshrao closed the pull request at:
https://github.com/apache/camel/pull/768
---
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 en
Hello everybody,
as I'm quite new to Camel I read a lot of documentation.
Thanks for providing it, most of it is very helpful. :)
I was wondering if the "available as of version" mentions for very old
versions should be removed? For example
http://camel.apache.org/cache.html mentions that cam
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/773
CAMEL-9498: Always provide a writable local registry (camel-2.16.x)
https://issues.apache.org/jira/browse/CAMEL-9498
plus some polish
You can merge this pull request into a Git repository by
GitHub user veithen opened a pull request:
https://github.com/apache/camel/pull/772
Fix sporadic test failures in camel-ssh and camel-ftp
In certain environments (in particular cloud environments), the unit
tests for camel-ssh and camel-ftp may quickly exhaust the Linux entropy
GitHub user snurmine opened a pull request:
https://github.com/apache/camel/pull/771
CAMEL-4725:Vendor spesific SQL type and removed type converters.
-Added ability to give SQL type code as integer in template instead of
String. This enables use Vendor specific SQL type.
-Remove
GitHub user sarwarbhuiyan opened a pull request:
https://github.com/apache/camel/pull/770
Rest elasticsearch client support
Added support for Elasticsearch Camel operations via HTTP (using Jersey).
Tried to keep as close to the operation specs based on the web
documentation but
Hi everyone,
I’ve just completed the work improving the Camel CDI component and open PR
https://github.com/apache/camel/pull/769.
As the open PR is quite large, I’ve documented the most important contributions
in https://issues.apache.org/jira/browse/CAMEL-9201.
For those interested, I’d like
Hi Claus,
If we mantain the re-run number on a default value of 2, we should be able to
notice potential issues.
In my opinion the PR is ok.
Thanks,
Andrea
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitte
Github user snurmine closed the pull request at:
https://github.com/apache/camel/pull/759
---
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
Hi
We got a PR pending at
https://github.com/veithen/camel/commit/6bcdb7f30f4984508fab6f683c3e4775bfc84a6e
I haven't seen that option before on the surefire plugin.
It seems at first glance as a nice way to work around any oddiness.
But wonder on the other hand if it would cause these "oddiness"
Github user hqstevenson closed the pull request at:
https://github.com/apache/camel/pull/763
---
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
Hello Quinn
Excuse me that I've missed your emails - your findings are interesting
- I'll try to test your scenarios tomorrow (Friday) morning CET. ok?
regards
Grzegorz
2016-01-14 16:42 GMT+01:00 Quinn Stevenson :
> Hi Grzegorz -
>
> So is this a bug? It seems like it is to me, but I don’t want
Hi Grzegorz -
So is this a bug? It seems like it is to me, but I don’t want to waste
anybody’s time with the JIRA if it isn’t and I’m just doing something stupid.
Quinn Stevenson
> On Jan 6, 2016, at 3:30 PM, Quinn Stevenson
> wrote:
>
> I just re-ran the test against several versions of C
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/769
CAMEL-9201: Improved Camel CDI component
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astefanutti/camel camel-cdi-pr
Alternatively you ca
19 matches
Mail list logo