5

我必须选择一种技术来连接我的应用程序/表示层（基于 Java）和服务层（基于 Java）。基本上是从业务委托对象中查找合适的 Spring Service。

那里有很多选择，这让我感到困惑。以下是我缩小范围但不确定的选项..

  • 弹簧 RMI

  • 阿帕奇骆驼

  • Apache ServiceMix (ESB)

  • 爱奥那保险丝 (ESB)

这是我想知道的

  1. 如果您从事过（或评估过）其中任何一项工作，您认为哪种选择更合适？（告诉我原因也无妨：）
  2. 还有其他我应该关注的技术吗？
  3. 到目前为止，我还没有看到应用程序和服务层正在分发，但我不想在将来排除这种可能性。设计以提供这种灵活性是一个好主意吗？

任何帮助都会很有用。谢谢！

4

3 回答 3

3

Spring Remoting would seem like the simplest approach. It also would leave you open to more complex approaches in the future if that is the direction you want to take.

From the limited view of your requirements, I would stick with a simple solution with a lower learning curve, and leave the ESB till you determine you actually need it.

The KISS principle is a wonderful thing.

于 2008-12-03T17:23:53.347 回答
2

它主要归结为您想使用 Spring Remoting（Spring RMI 和Apache Camel是其实现） - 还是您想将 JAX-WS 用于 Web 服务（CXF 或 Metro 实现）。即，您是否想要为您的 POJO 自动远程处理 - 或者您是否想要带有 WSDL 合同的 WS 等等。

Once you've decided on the remoting technology; your next decision is do you want to bundle it inside your application as a library (e.g. Spring RMI or Camel) - or do you want to deploy it in an ESB container like ServiceMix to be able to hot-redeploy modules and so forth.

If the latter is your choice then use Apache ServiceMix - or use the FUSE ESB if you want a commercial distribution with more documentation, frequent releases, commercial support and so forth.

于 2008-12-03T16:46:28.023 回答
2

Here you can find a simple solution to integrate Metro and Camel together: http://www.everit.biz/web/guest/everit-blog/-/blogs/calling-a-camel-route-from-web-service-using-metro-and-tomcat?_33_redirect=/web/guest/everit-blog

于 2010-07-01T14:40:13.600 回答