What's wrong with using selectors? You are using a shared queue for different
endpoints, so in my opinion that's a very good reason for using a selector. How
do you want to dispatch your reply messages to different endpoints without
selectory?
-Original Message-
From: James Carman [mai
The Apache Jenkins build system has built Camel.trunk.notest (build #2811)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2811/
to view the results.
GitHub user mzipay opened a pull request:
https://github.com/apache/camel/pull/1075
CAMEL-10038 don't throw exception if BlueprintPropertiesParser#parsePâ¦
â¦roperty would return null (breaks fallbackToUnaugmentedProperty
behavior, and an exception will be thrown anyway by the par
Dear Apache Enthusiast,
As you are no doubt already aware, we will be holding ApacheCon in
Seville, Spain, the week of November 14th, 2016. The call for papers
(CFP) for this event is now open, and will remain open until
September 9th.
The event is divided into two parts, each with its own CFP. T
Hi
I started an experiment a while back, and it has been sitting on my
laptop for a while. I recently discussed this work with Clement and
Charles at RH event in Newcastle.
So I dusted off this code and pushed it upstream in the eventbus
branch. Mind that it's not rebased so it does not track all
Shared uses selectors. There's no reason to use selectors in my case
On Wed, Jul 13, 2016 at 6:31 AM Siano, Stephan
wrote:
> If you want to share a replyTo queue the replyToType is Shared, not
> Exclusive, so this should already be supported, or do I geth something
> wrong here?
>
> -Origina
If you want to share a replyTo queue the replyToType is Shared, not Exclusive,
so this should already be supported, or do I geth something wrong here?
-Original Message-
From: James Carman [mailto:ja...@carmanconsulting.com]
Sent: Dienstag, 12. Juli 2016 15:47
To: dev@camel.apache.org
Su
