Return-Path: <users-return-60903-archive-asf-public=cust-asf.ponee.io@camel.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id BFFE3200828
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Fri, 13 May 2016 14:12:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id BE9C916099F; Fri, 13 May 2016 12:12:22 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 12E911602C0
	for <archive-asf-public@cust-asf.ponee.io>; Fri, 13 May 2016 14:12:21 +0200 (CEST)
Received: (qmail 96578 invoked by uid 500); 13 May 2016 12:12:21 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Delivered-To: moderator for users@camel.apache.org
Received: (qmail 95556 invoked by uid 99); 13 May 2016 12:09:48 -0000
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 3.736
X-Spam-Level: ***
X-Spam-Status: No, score=3.736 tagged_above=-999 required=6.31
	tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_ENVFROM_END_DIGIT=0.25,
	NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001,
	SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled
Date: Fri, 13 May 2016 05:09:44 -0700 (MST)
From: ravi21588 <ravi21588@gmail.com>
To: users@camel.apache.org
Message-ID: <1463141384751-5782554.post@n5.nabble.com>
Subject: Query in using Dynamic router EIP
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 13 May 2016 12:12:22 -0000

Hi All,

I have a query related to dynamic router EIP.

The diagram in camel site shows the EIP has a Dynamic rule base store  and =
a
control channel .

I just saw the implemented example in Documentation

<bean id=3D"mySlip" class=3D"org.apache.camel.processor.DynamicRouterTest"/=
>
=C2=A0
<camelContext xmlns=3D"http://camel.apache.org/schema/spring">
=C2=A0=C2=A0=C2=A0=C2=A0<route>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<from uri=3D"direct:start"/=
>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<dynamicRouter>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<me=
thod ref=3D"mySlip" method=3D"slip"/>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0</dynamicRouter>
=C2=A0=C2=A0=C2=A0=C2=A0</route>
=C2=A0
=C2=A0=C2=A0=C2=A0=C2=A0<route>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<from uri=3D"direct:foo"/>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<transform><constant>Bye Wo=
rld</constant></transform>
=C2=A0=C2=A0=C2=A0=C2=A0</route>
=C2=A0
</camelContext>


and the java bean mySlip handles the logic which=20

/**
 * Use this method to compute dynamic where we should route next.
 *
 * @param body the message body
 * @return endpoints to go, or <tt>null</tt> to indicate the end
 */
public String slip(String body) {
    bodies.add(body);
    invoked++;
=20
    if (invoked =3D=3D 1) {
        return "mock:a";
    } else if (invoked =3D=3D 2) {
        return "mock:b,mock:c";
    } else if (invoked =3D=3D 3) {
        return "direct:foo";
    } else if (invoked =3D=3D 4) {
        return "mock:result";
    }
=20
    // no more so return null
    return null;
}


can you please tell what is acting as a control channel and Dynamic rule
base store.

Does Dynamic rule base store means persistent data store?


Also in the EIP Book says as below.

During system start-up, each potential recipient sends a special message to
the Dynamic Router on this control channel, announcing its presence and
listing the conditions under which it can handle a message. The Dynamic
Router stores the 'preferences' for each participant in a rule base. When a
message arrives, the Dynamic Router evaluates all rules and routes the
message to the recipient whose rules are fulfilled. This allows for
efficient, predictive routing without the maintenance dependency of the
Dynamic Router on each potential recipient.

Can you please tell how does it happens?




--
View this message in context: http://camel.465427.n5.nabble.com/Query-in-us=
ing-Dynamic-router-EIP-tp5782554.html
Sent from the Camel - Users mailing list archive at Nabble.com.