Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of bruno.borges@gmail.com
 designates 209.85.217.160 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=NTjke6T3OLz0oHz7ZEkNI+rqDhP1fe9QKT3linIRt00de+cUJSObDk64SdpxMbC9By
         HEIoZIyMQS0F0NfOlUW23h4clo1pPZT9sLfznZGHinWUtgqz4LZEnoPefLZH7kTYbbv4
         61yF6s3LQ6V6LFe0J1eW1cmcZOm0zlOA8e96A=
MIME-Version: 1.0
In-Reply-To: <22578949.post@talk.nabble.com>
References: <22370230.post@talk.nabble.com>
	 <ec6e67fd0903060415v592e76bex493f89d7c4c70f0@mail.gmail.com>
	 <22522393.post@talk.nabble.com>
	 <5380c69c0903160921i2305c1d7sbe7e4a65c15c673d@mail.gmail.com>
	 <22578949.post@talk.nabble.com>
Date: Thu, 19 Mar 2009 10:12:56 -0300
Message-ID: <91c14fa90903190612y7aa6489dy9b0a9f9ce4e05dec@mail.gmail.com>
Subject: Re: Starting, stopping and removing routes at runtime
From: Bruno Borges <bruno.borges@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=00221532cba0041a4e0465788f8b

--00221532cba0041a4e0465788f8b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I'm sorry I'm getting this thread in the middle without reading previous
messages, but just one thought: isn't this what ESBs are supposed to manage?

I mean, with ESBs we can plug'n play routes easily, add, remove, whatever.
If Camel start to have functions like this, wouldn't be overlapping with
ESBs functions?

How would Camel compare with ServiceMix for example?

Please don't shoot. :-)

Best regards,
Bruno Borges
blog.brunoborges.com.br
+55 21 76727099

"The glory of great men should always be
measured by the means they have used to
acquire it."
- Francois de La Rochefoucauld


On Wed, Mar 18, 2009 at 10:15 AM, m.s. <da_bus@arcor.de> wrote:

>
>
>
> >> - can I get a single RouteDefinition, or only a list that I must iterate
> >> to
> >> find the one I am looking for?
> > The API is what we got. But we are open for API changes in Camel 2.0
> > so if you have suggestions what
> > you would like changed/added that feedback is much appreciated.
> >
>
> I think a pre check if a route with a certain ID already exists would be
> helpful. I would also like to do more things based on the routeID, instead
> of getting the list with the RouteDefinitions and then searching for the
> one
> I want to manipulate. I am thinking about methods like
> - RouteDefinition getRouteDefinition(String id)
> - void startRoute(String id)
> - void stopRoute(String id)
> - boolean routeExists(String id)
>
> On the other hand I am not sure if this is really feasible as the route ID
> is an optional attribute. And as these route manipulations at runtime do
> not
> occur that often, the current API and some additional code in the
> application is probably sufficient in most cases.
>
> M.S.
> --
> View this message in context:
> http://www.nabble.com/Starting%2C-stopping-and-removing-routes-at-runtime-tp22370230p22578949.html
> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
>
>

--00221532cba0041a4e0465788f8b--