关键点恕我直言不是功能之一。在这方面，Spring将始终领先于JavaEE，因为它对OpenSource VS来说是很自然的。标准。因此，有一个事实是，使用Java可以更早地获得新功能（例如，容器集成测试是JavaEE 6中的一项新功能，并且已经在Spring中使用了很长时间）。

The crucial point IMHO is not the one of features. In that regard, Spring will always be ahead of JavaEE as it's natural for OpenSource VS. a Standard. So one fact is, that you get the new features much earlier with Spring that with JavaEE (e.g. container integration testing is a new feature in JavaEE 6 and has been available in Spring for ages).

最重要的一点是恕我直言，是管理和发展的生命周期之一。选择JavaEE时，可以将编程模型与基础架构联系起来。通常，应用服务器供应商并不是采用新标准版本的最快版本（归咎于WebSphere，JBoss，你有什么）。所以这意味着我们可能不会看到生产准备就绪，JavaEE 6在年底前支持大型供应商的产品。

The most important point IMHO is the one of lifecycles for administration and development. When you choose JavaEE, you tie your programming model to your infrastructure. Usually app server vendors are not the fastest adopting new standard's versions (blame WebSphere, JBoss, what have you). So this means we probably won't see production ready, JavaEE 6 supporting products by the big vendors before end of the year.

即使是这种情况，您仍然需要担任管理层，IT部门和预算控制经理的障碍，愿意升级到这个闪亮的新版本。从这一方面来看，JavaEE 6甚至不是许多商店的选择。您可以选择将应用程序部署到何处？你想选择Glassfish进行生产吗？来吧，试试吧。大多数商店都没有处于这种舒适的状态。

Even if that is the case then you still have to take the hurdle of your administration, IT department and budget controlling managers to be willing to upgrade to this shiny new version. Coming from this side, JavaEE 6 is not even an option to many shops. You can choose what ever you like to deploy your apps to? You wanna choose Glassfish for production? Go ahead, try. Most shops aren't in such a "comfortable" situation.

完全相反：春天。从基础设施中解耦编程模型。转到当前的3.0.x并在Tomcat或遗留应用程序服务器中使用 @Inject ，JPA 2等。

Exactly contrary: Spring. Decoupled programming model from infrastructure. Go take current 3.0.x and use @Inject, JPA 2 and the like in your Tomcat or legacy application server.