Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.191.145.13
 which is an MX secondary for dev@camel.apache.org)
MIME-Version: 1.0
References: <1430148878115-5766390.post@n5.nabble.com>
 <etPan.553ed9a1.74b0dc51.116@localhost>
 <1430193009145-5766412.post@n5.nabble.com>
In-Reply-To: <1430193009145-5766412.post@n5.nabble.com>
From: Henryk Konsek <hekonsek@gmail.com>
Date: Tue, 28 Apr 2015 12:49:23 +0000
Message-ID: 
 <CALhQg-Y76NE8ywcFdnjc6B8zMSu=suERkNHZkBqk_6buOqX+0Q@mail.gmail.com>
Subject: Re: Camel resequencer() is not working inside choice - java dsl
To: dev@camel.apache.org
Content-Type: multipart/alternative; boundary=20cf301ee581c4b3610514c84a59

--20cf301ee581c4b3610514c84a59
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

Regarding 1) - you don't have to know the endpoints upfront because you can
connect resequencer to the Recipient List using the direct endpoint. Just
as Willem demonstrated.

Cheers.

wt., 28.04.2015 o 06:38 u=C5=BCytkownik Sumit <summ.chakraborty@gmail.com>
napisa=C5=82:

> Hi,
>
> Thanks for your quick reply.
>
> We have following concerns:
>
> 1. .to() will not fit in our case as we dont know the endpoint uris
> earlier.
> I determine the endpoints as java Set. So is there any workaround for thi=
s?
>
> 2. If we put the messages in another queue after resequencing and run the
> followinf code ---from(=E2=80=9Cdirect:A=E2=80=9D).recipientList(...)  --=
- concurrently
> (mutiple threads) then will it maintain the same sequence.
>
> Your quick response is highly appreciated.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-resequencer-is-not-working-inside=
-choice-java-dsl-tp5766390p5766412.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>

--20cf301ee581c4b3610514c84a59--