The behaviour seems to be different for a nested route with a seda consumer.
At least my two test cases are working when I use NotifyBuilder on the
nested route with the seda consumer.
--
View this message in context:
http://camel.465427.n5.nabble.com/An-issue-with-NotifyBuilder-on-nested
omEndpointDirect() {
> NotifyBuilder nb = new
> NotifyBuilder(context).from("direct:doStuffNow").whenDone(1).create();
> Exchange exchange = new DefaultExchange(context);
> exchange = template.send("direct:a", exchange);
> boolean done = nb.matches(5, TimeUnit.SECONDS);
> assertTrue("Timed out waiting for notify builder
> from(seda:doStuffNow)", done);
> }
> }
> ---
>
> Kind regards
> Søren
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/An-issue-with-NotifyBuilder-on-nested-routes-tp574.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
ect() {
NotifyBuilder nb = new
NotifyBuilder(context).from("direct:doStuffNow").whenDone(1).create();
Exchange exchange = new DefaultExchange(context);
exchange = template.send("direct:a", exchange);
boolean done = nb.matches(5, TimeUnit.SECONDS);
