camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Khai Nguyen <>
Subject Re: A silly idea?
Date Thu, 14 Jan 2016 19:29:13 GMT
I have been using Camel at work for sometimes and I love Camel.

Here, we think about Camel having 2 pieces: *component* (I use this term
loosely to mean non-route) which is written only in code and *route* which
could be written in any particular DSL (groovy, java, xml,...).

The component is fixed in term of deployment. The route becomes the hot
deploy unit. You can do

   1. OSGI if your route is in java DSL or any JVM language, because it is
   a jar now.
   2. A simple route deployer if your route is in XML or Groovy.
   3. ...

Our application is just a simple java application with /lib and /route
directories and a shell script to run the main method.

We wrote a maven archetype to generate our standard minimal (cuz we don't
want to ship 1GB of useless jar) camel project. Then you add more
components depend on what your application have to do. Then we ship the

Camel, at core, is just a integration library allows you to send
datas/commands/requests from a endpoint to a endpoint(s).

On Thu, Jan 14, 2016 at 10:40 AM Christian Schneider <> wrote:

> The problem is that people have different requirements for the runtime.
> For example the hot deployment is a reason to choose OSGi but not everyone
> needs that.
> You should have a look at Apache Karaf. It might provide just the
> environment you search for.
> I got a tutorial that shows how to deploy your camel integrations to Apache
> Karaf. It is quite simple and straight forward.
> Btw. I just noticed that my tutorial covers a quite ancient version of
> karaf. I will update it for the new karaf 4 command syntax.
> There are also some offerings from companies that build on Apache Karaf and
> provide some add on functionality like
> Talend ESB or Jboss Fuse. You can do most things with just the open source
> version though.
> Christian
> 2016-01-14 7:37 GMT+01:00 Kay <>:
> > Hello, I'm new to this forum, but I've used camel for a long time. ( as a
> > matter of fact, I can't imagine the thing that I am able to do my java
> > project without camel ). Anyway, a question teased me whenever I use
> Camel.
> > The question was "why is there no base framework for only camel?" In the
> > other word, I believe it would be better if there was a certain
> > light-weighted environment supporing camel with some better
> functionalities
> > like concurrency, extensibility, hot deploy. So, when I told my colleague
> > about this idea, he replied, "Use zookeeper for failure tolerance, use
> > for hot deploy, use Storm or Spark for data distribution. You don't need
> to
> > build another similar thing for your own purpose." But I can't make
> certain
> > with his words because I can't understand the reason why I should control
> > so
> > many applications for my project. I just want a light-weighted all-in-one
> > package. Is building such an all-in-one package for camel a silly idea?
> How
> > do you think about that?
> >
> >
> >
> > --
> > View this message in context:
> >
> > Sent from the Camel - Users mailing list archive at
> >
> --
> --
> Christian Schneider
> <
> >
> Open Source Architect
> <
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message