Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.215.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1339496303501-5714340.post@n5.nabble.com>
References: <1336050743758-5683138.post@n5.nabble.com>
 <CAGB5yNm+QU6UGQczgNZWF+Q8eoznPHZ=TFDus__SxP9wmu=Tcw@mail.gmail.com>
 <1339164802844-5714209.post@n5.nabble.com>
 <CAGB5yNkfYsF0HPT=vkx6cojSA6B-T4cC2w24JMg+EdnkwwyqHg@mail.gmail.com>
 <1339496303501-5714340.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 12 Jun 2012 12:41:04 +0200
Message-ID: 
 <CAGB5yNn_uBOXr2ytH3DN2dUXtvjYqqJg317z8EVNRwdZdfn6cg@mail.gmail.com>
Subject: Re: No hit during Multicast
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=bcaec54c513ab1bd6b04c2441b21

--bcaec54c513ab1bd6b04c2441b21
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 12, 2012 at 12:18 PM, kenhans <kenhansa@hotmail.co.uk> wrote:

> yes, I see that my description of the filter is lacking. It's actually a
> loop
> like this, where the producers contain filter-methods:
>
> MulticastDefinition multicastDefinition = route.multicast().onPrepare(new
> DocumentDeepClone());
> for (Producer producer : producers) {
>  multicastDefinition
>   .filter().method(producer, "filter")
>  .bean(producer, "createEvent")
>  .to(EndPointUri.INCOMING_EVENT_QUEUE);
> }
>
> so my problem is that the Exchange is not forwarded to the destination
> (.bean...) if the filter Predicate of all Producers are false. And I do not
> know how to handle that case. I do not seem to have any handle to the
> Exchange after all predicates are false. How would the AggregationStrategy
> help me here? I just want to discover the special case when all filter
> predicates of the producers are false
>
>
You can set a special header in the .bean, and detect if that header is
absent in your aggregation strategy.
Then you know all the filters was false.

Another way is that Camel sets the
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html#TO_ENDPOINT
header when you send a message to a destination using .to and some of the
other EIPs.
So if that header has not changed then all your filters is also false.


>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/No-hit-during-Multicast-tp5683138p5714340.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>


-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

--bcaec54c513ab1bd6b04c2441b21--