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.
