RE: Runtime advice

["Pitre, Russell" <RP...@shawmut.com>]

Thanks for the feedback, I'll take your advice and run with it....I like the fact you suggested to keep it simple; I'm a firm believer in the KISS principle.

-Russ

-----Original Message-----
From: Claus Ibsen [mailto:claus.ibsen@gmail.com] 
Sent: Friday, February 26, 2010 12:16 PM
To: users@camel.apache.org
Subject: Re: Runtime advice

On Fri, Feb 26, 2010 at 5:51 PM, James Strachan
<ja...@gmail.com> wrote:
> On 26 February 2010 16:46, Pitre, Russell <RP...@shawmut.com> wrote:
>> I'm about to start a new integration project using Camel.  I'd like to
>> survey what my runtime options are.  My preliminary research has lead me
>> to using a Servlet container such as Tomcat or a OSGI container such as
>> Apache Felix or dm Server.  I don't have any experience with OSGI, the
>> limited experience I do have has been frustrating to say the least.  So
>> I'm wondering if Tomcat would suffice my requirements.
>
> My advice is always to start with Tomcat and stay there until you find
> you've a requirement which means you've gotta go OSGi, just because
> its so much easier to work with.
>
> You can start & stop routes and edit them at run time easily -
> particularly using the web console...
> http://camel.apache.org/web-console.html
>

You can also use JMX to manage your routes, such as starting, stopping
and what not
http://camel.apache.org/camel-jmx.html

Maybe your organization already have monitor applications which can
remote manage Tomcat over JMX. Then that will allow you to use that
app to mange your Camel app as well.


> the main reason for starting/stopping a web app is if you need to
> change the Java code.
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>



-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus