There's a few ways to look at things really. IMHO the main power of Spring Integration is the annotations on beans to declare some EIP routes. The power of Camel in my massively biased view is the powerful underlying model of EIPs which can be created via Spring XML, Java code or Scala (which should also lead to some amazing visualisation & debugging tooling soon...), the powerful underlying message model and the ton of components and pattern implementations.
So I see the two being able to work quite nicely focussing on different perspectives. Camel focusses on being a large, active open source project to create a ton of patterns and components along with a powerful EIP model capable of implementing any EIP routes - Spring Integration so far seems to focus on creating annotations that can be used inside beans to implement some EIPs. Right now there's two ways to look at the marriage of Camel and Spring Integration: reusing Camel components, endpoints or routes with Spring Integration beans; or reusing Spring Integration's bean annotation model from within Camel routes. They are kinda different approaches to integration; but most importantly they both integrate with each other pretty well :) so we can mix and match them as we see fit 2008/5/28 cmoulliard <[EMAIL PROTECTED]>: > > Many thanks for your reply. > > Some of the benefits that you mention must be addressed carefully due to a > limitation of the current Spring Integration Architecture. > > The communication between Spring Integration endpoints is only JMS based > (Spring provides a JMSSource and JMSGateway adapters) and does not allow to > use SEDA or DIRECT flows between endpoints. This limitation reduces the > architecture that we can design top of spring ESB because every time a > message will left the Camel endpoint service, it must be placed into a JMS > queue and we cannot use VM/DIRECT/SEDA. > > Charles > > > willem.jiang wrote: >> >> Hi Charles, >> >> If you are big Spring fan and have lots of Spring bean's in your >> application world , you could take advantage of the first benefit that >> you listed in your mail. >> And you can get more that. Since Camel has lots of components which >> could not be implemented by Spring Integration as the customer adapters, >> you could find Camel extends the Spring Integration's connectivity. >> >> Although Camel provides some ways to invoke the Spring beans endpoints, >> but I should say Spring Integration make it more easier, so you can >> leverage the message routing pattern within Camel and Spring bean >> invocation within Spring Integration. >> >> I think the combination of Camel and Spring Integration using , could >> give you a more powerful tool for enterprise application integration :). >> >> Any thoughts? >> >> Willem >> >> cmoulliard wrote: >>> Hi, >>> >>> What are the benefits to use Camel with spring-integration endpoints ? >>> >>> - Combination of the power of the Camel EIP routing with a lightweight >>> ESB >>> bus ? >>> - Provide an alternative to deploy Camel routing engine in a different >>> ESB >>> bus than ServiceMix ? >>> - ..... >>> >>> Charles >>> >> >> >> > > -- > View this message in context: > http://www.nabble.com/Benefits-to-use-Camel---Spring-Integration-tp17507570s22882p17509264.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
