Re: thinking in the difference between camel and servicemix

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.

Re: thinking in the difference between camel and servicemix

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,

Re: thinking in the difference between camel and servicemix

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://servicemi

Re: thinking in the difference between camel and servicemix

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/2705