You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by ltomuno <lt...@163.com> on 2011/06/05 05:34:45 UTC
thinking in the difference between camel and servicemix
camel is a component, servicemix is a container
from function
servlet container(e.g. tomcat) < application container(e.g. jboss) < esb container(e.g. servicemix)
in one sense, esb is a more powerful container than application container, contains the EIP functions, and can provide outside services alone, but camel can't, it just a classic component
Do I thinking correct?
thanks
Re: thinking in the difference between camel and servicemix
Posted by Ashwin Karpe <ak...@fusesource.com>.
Hi,
As Claus mentioned correctly the servicemix components are legacy components
grounded in the JBI spec. They are also rather dated and no longer as useful
since JBI spec is no longer being actively updated. The latest Servicemix
container is OSGi based both still supports the legacy components. Camel
components are on the other hand foundationally different entities and more
recent/up-to-date.
If you are interested in understanding the differences for purely
understanding purposes, please check out my blog entry (circa 2009) to get a
sense of the differences.
http://opensourceknowledge.blogspot.com/2009_07_01_archive.html Things to
consider when selecting between Apache Camel and Servicemix
I would strongly advise using Camel components if you have a choice...
Cheers,
Ashwin...
-----
---------------------------------------------------------
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com
Blog: http://opensourceknowledge.blogspot.com
CamelOne 2011: http://fusesource.com/camel2011
---------------------------------------------------------
--
View this message in context: http://camel.465427.n5.nabble.com/thinking-in-the-difference-between-camel-and-servicemix-tp4455513p4475801.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: thinking in the difference between camel and servicemix
Posted by Claus Ibsen <cl...@gmail.com>.
The SMX components are JBI components and in SMX 4.x+ they are legacy.
See this blog about JBI being dead/legacy
http://gnodet.blogspot.com/2010/12/thoughts-about-servicemix.html
In SMX 4.x+ Camel is the preferred routing engine. So use Camel and
use SMX to host your Camel apps.
On Mon, Jun 6, 2011 at 1:55 PM, bvahdat <ba...@swissonline.ch> wrote:
> Hi Claus,
>
> a similar question while comparing Apache Camel & Apache ServiceMix came
> also into my mind many times. Somehow I've got the feeling that the wheel
> has been reinvented either by ServiceMix or Camel! Just as an example what's
> your opinion about the following two "wheels"?
>
> http://servicemix.apache.org/servicemix-file.html
> http://camel.apache.org/file2.html
>
> As another example:
> http://servicemix.apache.org/servicemix-quartz.html
> http://camel.apache.org/quartz.html
>
> And so on... and so on
>
> They all seem pretty similar, don't they? What am I really missing to really
> understand these "wheels"?
>
> Regards, Babak
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/thinking-in-the-difference-between-camel-and-servicemix-tp4455513p4458446.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: thinking in the difference between camel and servicemix
Posted by bvahdat <ba...@swissonline.ch>.
Hi Claus,
a similar question while comparing Apache Camel & Apache ServiceMix came
also into my mind many times. Somehow I've got the feeling that the wheel
has been reinvented either by ServiceMix or Camel! Just as an example what's
your opinion about the following two "wheels"?
http://servicemix.apache.org/servicemix-file.html
http://camel.apache.org/file2.html
As another example:
http://servicemix.apache.org/servicemix-quartz.html
http://camel.apache.org/quartz.html
And so on... and so on
They all seem pretty similar, don't they? What am I really missing to really
understand these "wheels"?
Regards, Babak
--
View this message in context: http://camel.465427.n5.nabble.com/thinking-in-the-difference-between-camel-and-servicemix-tp4455513p4458446.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: thinking in the difference between camel and servicemix
Posted by Claus Ibsen <cl...@gmail.com>.
Yeah thats one way of seeing the world.
There is a FAQ
http://camel.apache.org/how-does-camel-compare-to-servicemix.html
http://camel.apache.org/how-does-camel-compare-to-servicemix-eip.html
Also stackoverflow have some QA about Camel and SMX. For example:
http://stackoverflow.com/questions/2705043/java-messaging-difference-between-activemq-mule-servicemix-and-camel
2011/6/5 ltomuno <lt...@163.com>:
> camel is a component, servicemix is a container
> from function
>
> servlet container(e.g. tomcat) < application container(e.g. jboss) < esb container(e.g. servicemix)
> in one sense, esb is a more powerful container than application container, contains the EIP functions, and can provide outside services alone, but camel can't, it just a classic component
> Do I thinking correct?
> thanks
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/