我们选择 Camel 而不是 Spring-Integration，因为 fluent API 非常好.我们实际上在Spring项目中使用它，并使用Spring来配置它的一部分.编程 API 很清楚，并且有大量合理的组件.

We choose Camel over Spring-Integration because the fluent API is really nice. We actually use it in Spring projects and use Spring to configure part of it. The programming API's are clear and there is a large set of sensible components.

我们进行了一次小规模的枪战，当时基本上满足了我们的要求，Camel 赢了.我们主要使用它来向/从外部传输内部数据文件，这通常需要使用 ftp/sftp/... 发送它或将其附加到电子邮件并发送出去.

We did a small scale shootout and basically at that time for our requirement Camel won. We use it mainly to transfer internal datafiles to/from external parties which usually requires format conversions sending it using ftp/sftp/... or attaching it to an email and sending it out.

我们发现编辑-编译-调试周期减少了.使用 groovy 来试验设置路由是额外的好处.

We found the edit-compile-debug cycle reduced. Using groovy to experiment setting up routes are added bonuses.

Spring-Integration 也是一个很棒的产品，我很确定它也能满足我们的需求.

Spring-Integration is a great product too, and I am quite sure it would satisfy our needs too.