通过添加camel功能扩展现有的spring应用程序
我的 Web 应用程序是用 Spring MVC 编写的。这是一个非常简单的应用程序，用于注册一些活动并在一段时间后生成报告。现在我已经在春天完全完成了。唯一的入口点是 HTTP webapp 请求。我想添加其他入口点，以允许用户通过 JMS 队列、FTP 文件和基于 SOAP 的 Web 服务触发应用程序。 我知道我可以使用 Spring 自己的功能以某种方式完成这一切，但我想知道是否需要将 Apache Camel 纳入所有这些内容中？ 我考虑让Web应用程序保持原样（直接与服务通信），只向Spring上下文添加一些Camel魔法并从Camel公开多个端点，然后在消息处理和转换之后调用现有服务。
我考虑使用 Camel 来使用一些异步处理和线程/可扩展性功能。这是正确的方法吗？
I have my web application written in Spring MVC. It is quite simple app for registering some activities and generating reports after some time. Now I have it done fully in Spring. The only entry point is HTTP webapp request. I'd like to add other entry points to allow user to trigger application via JMS queue, FTP files and SOAP-based web service.
I know I can do this all using Spring own features somehow, but I wonder if it is desirable to involve Apache Camel into all that stuff?
I think about leaving web application as it is (communicating directly with services), only add some Camel magic to spring context and expose several endpoints from Camel and then after messages processing and transformations call existing services.
I think about using Camel to be able to use some asynchronous processing and threads/scalability features. Is it the right way to go?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我会推荐你使用 Apache Camel。我已经将它用于类似的目的。从“关注点分离”的角度来看，该解决方案是合适的。 Camel实现了Enterprise Integration Patters，是集成各种协议和接口的更好的解决方案。您的应用程序应该只处理功能，并且按照设计应该只公开 servlet 来获取请求并处理它。
Camel 中接口和协议的处理结构良好，从长远来看易于维护和配置。
I will recommend you to use Apache Camel. I have used it for a similar purpose. The solution is an appropriate one from a 'Separation of Concerns' point. Camel implement Enterprise Integration Patters and is a better solution for integrating various protocols and interfaces. Your application should deal with functionality only and as designed should just expose a servlet to get requests and process it.
Handling of interfaces and protocols are well structured in Camel and its easy to maintain and configure in the long run.