Re: cdi reuse the route

Hi Antonin, thanks a lot for help! I tried to play with it and get: ContextName is not repeatable annotation type. Are there any working examples using the same cdi route twice? Cheerz! -- View this message in context: http://camel.465427.n5.nabble.com/cdi-reuse-the-route-tp5788716p5789985.h

Re: cdi reuse the route

Hi, What CDI runtime are you using? It may be that some older runtimes do not support this. It has been discussed and is tracked in https://issues.jboss.org/browse/CDI-471 though some Weld versions already support it. Antonin > On 10 Nov 2016, at 09:59, a746076drdrb wrote: > > Hi Antonin, >

Re: Time for an overhaul of the patterns symbols?

Hi Tadayoshi, Thanks for your feedback. Maybe I was hasty in implying there might be differences in style. Looking again I see the logic to the different forms in the patterns. Initially I saw differences in line widths and colors, differences in types of coloring (gradient vs flat, border vs no b

[GitHub] camel pull request #1260: CAMEL-10463: Update Camel Salesforce integration t...

GitHub user zregvart opened a pull request: https://github.com/apache/camel/pull/1260 CAMEL-10463: Update Camel Salesforce integration tests Tests in SalesforceComponentConfigurationTest were not updated to the latest functionality provided by the SalesforceComponent::complet

Re: cdi reuse the route

I'm using org.jboss.weld.se weld-se 2.4.0.Final

Re: cdi reuse the route

That should be fine with that version of Weld. Though I realise for it to work the qualifier need to be annotated with @Repeatable, which is missing. I’ve just created https://issues.apache.org/jira/browse/CAMEL-10464. I’ll work on it ASAP. In the meantime, you should be able to achieve the same

[GitHub] camel pull request #1261: CAMEL-10462: Improve MDC Logging in DefaultCamelCo...

GitHub user hqstevenson opened a pull request: https://github.com/apache/camel/pull/1261 CAMEL-10462: Improve MDC Logging in DefaultCamelContext and RouteService I added nested classes to help with the MDC logging (to avoid a bunch of duplicate code). The nested classes have some d

Re: Help in testing a custom processor

Hi, thanks for your reply. I took a different direction because I felt that writing a custom appender was overengineering a bit. I have gotten the Log4j2 properties to work in order to write the logs into a file and have written two utilities: one for reading the Logs from the abovementioned file a

Proposed change to BlueprintCamelContext startup behaviour

I’d like to propose changing the BlueprintCamelContext such that the Camel Context is started when the Blueprint container is fully created. While working on CAMEL-9570 ( https://issues.apache.org/jira/browse/CAMEL-9570 ), I noticed that the Bl

[GitHub] camel pull request #1262: Fixed some javadoc warnings for camel-core

GitHub user aldettinger opened a pull request: https://github.com/apache/camel/pull/1262 Fixed some javadoc warnings for camel-core This PR proposes some javadoc warning fixes. Let me know if a JIRA ticket is needed before opening a pull request. Would this PR affects too many file,

[GitHub] camel pull request #1263: CAMEL-10178: Added Google PubSub Component

GitHub user evmin opened a pull request: https://github.com/apache/camel/pull/1263 CAMEL-10178: Added Google PubSub Component Google PubSub component with producer and consumer endpoints, unit and integration tests. Speed optimisation (mini batching, async processing) will be done