The Apache Jenkins build system has built Camel.2.17.x.notest (build #158)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/158/
to view the results.
GitHub user bkuzmic opened a pull request:
https://github.com/apache/camel/pull/1340
CAMEL-10582: Fixing copying of immutable Spring headers
Please consider merging this fix to allow complete Spring integration work
correctly.
You can merge this pull request into a Git repository
Take a look at camel-metrics. You can use a route factory where you
can then configure it once, and then it can add those route policy for
those routes where you use that given endpoint.
On Fri, Dec 9, 2016 at 3:19 PM, Claus Ibsen wrote:
> Hi
>
> Yes AFAIR that was not
Hi
Yes AFAIR that was not support today. That was what the ticket was
about. I managed to find it
https://issues.apache.org/jira/browse/CAMEL-3183
However that api change was likely to invasive. We can cope up with a
better api, where a consumer could maybe implement some interface for
having
Thank You Claus - but I must not have stated my question very well ;-)
I’m working on a custom Camel component - and Event Driver Consumer to be
precise. When the component starts-up, I’d like to get the Camel route ID of
the route that is using the component.
I’m extending
GitHub user Fabryprog opened a pull request:
https://github.com/apache/camel/pull/1339
Camel 10560
hello,
to able to access new method getSubmittedFileName() (it is not in
datasource interface) change class's visibility.
Without this fix a cannot access to new method
You can use a RoutePolicy which has callbacks when routes are
initialized / started etc where you can get hold of the endpoint.
There is a JIRA about allowing a consumer to be endpoint aware. But I
think this required some API changes and was deferred for Camel 3.x.
On Fri, Dec 9, 2016 at