I had asked a similar question on the Spring Integration forum http://forum.springframework.org/showthread.php?t=49654
There appears to be a lot of interest in this topic, but I'm not sure there's "1" easy answer that will generally satisfy everyone given the unique environments involved with each particular usage situation. I'd certainly like feedback from other's on what they see as pros/cons -- without any bashing of course :) -- but I've decided just to dig into the source code and start playing. That said, I've found James' blog http://macstrac.blogspot.com/ helpful as well as a presentation he did on Camel a short while ago...http://macstrac.blogspot.com/2007/11/my-slides-on-activemq-and-camel-from.html I've also found the current Spring Integration reference doc http://static.springframework.org/spring-integration/reference/htmlsingle/spring-integration-reference.html helpful. What I really like about Camel so far is RouteBuilder as well as the large number of currently supported components. I also really like the helpful mailing list. What Spring Integration is younger and hasn't yet reached 1.0, so far I really like what I see in the source code, the straightforward abstractions, and Mark Fisher's openness and helpfulness. Working with the SVN repo and Ant/Ivy has also been very nice as I'm not Maven-Converted(TM) yet. For what it's worth, I think both projects look great which makes the decision harder :) Jon Patrick Munis wrote: > > How does camel compared to spring integration ? Are they complementary > technology? > > PM > > -- View this message in context: http://www.nabble.com/Spring-Integration-tp15717186s22882p15725150.html Sent from the Camel - Users mailing list archive at Nabble.com.
