Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <22800241.1198846950609.JavaMail.jira@brutus>
Date: Fri, 28 Dec 2007 05:02:30 -0800 (PST)
From: "Hadrian Zbarcea (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-280) Dynamic Router implementation
In-Reply-To: <14593751.1198830747682.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/CAMEL-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40929 ] 

Hadrian Zbarcea commented on CAMEL-280:
---------------------------------------

Great initiative!

I think we'll need to think a bit about this one.  AFAIK, the intent behind CAMEL-8 is to support the following scenario:
* client sends message to router (camel)
* camel processes and send to a server, server replies, but the response contains a service url (e.g. a 'createAccount' operation that returns the url for the newly created Account service).  Now the issue is that the new url may be of no use to the client for quite a few reasons, for instance client may not support the protocol - but camel does - or the server may be behind a firewall, accessible to camel, but not to the client)
* camel creates new endpoint and deploys route to the new service, modifies the response to send its own url back to the client
We can implement a control feature in camel to support dynamic creation and deployment of routes.

>From looking at your patch, i am not sure how it's different than using a Processor.  Do I miss something?  How is your scenario different from CAMEL-8?

I'll be out for a week, but I'd be more than happy to tackle this one when back.  Happy New Year!

> Dynamic Router implementation
> -----------------------------
>
>                 Key: CAMEL-280
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-280
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Przemyslaw Budzik
>            Priority: Minor
>             Fix For: 1.3.0
>
>         Attachments: dynamic-router.patch
>
>
> I decided to get my hands dirty by taking https://issues.apache.org/activemq/browse/CAMEL-8 :) I had in mind a feature like this:
> from("....").dynamicRouter(myRouter);
> where myRouter is a class that implements some interface so that it provides a list of endpoints (or one endpoint as well) to send messages to. Of course it creates some room for further improvements like providing Drools integration or another sophisticated routing mechanism based on "rules" so to speak. The idea is to have message and depending on its content create destinations dynamically per flow. 
> Anyway when expressed by DSL it's quite nice to use (however still the same is doable playing with processors). What do you think about it? Does it make sense?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.