Hi Jeroen, ServiceMix 4.x is a server designed top of OSGI framework. The modularity offered by OSGI allows that our server runs different kind of container Spring, Camel, JBI, Web applications, ...
So depending of your peoject requirements, you can build a solution using JBI specification (= bus where all the messages are XML, routing between components exchanging messages through the normalized bus (=NMR) can be done using servicemix-eip or servicemix-camel) or Camel (= routing engine allowing to route objects in message through different processors. In this case, we work with objects). Kind regards, Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel - ServiceMix Committer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Blog : http://cmoulliard.blogspot.com | Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard On Wed, Jul 14, 2010 at 5:09 PM, Jeroen Verhagen <[email protected]>wrote: > Hi all, > > In evaluating ServiceMix I found that a lot of the functionality > offered by the different components of SM are also available in Camel > (file, ftp, transformation, eip, jms etc.). So if you already need > Camel in your SM project, for example for advanced message routing, > what would be the advantage of using the SM 'native' components > instead of solving all problems in Camel? > > -- > > regards, > > Jeroen >
