Spring 3.0 vs Java EE 6.0 [英] Spring 3.0 vs Java EE 6.0

问题描述

我遇到了一种情况...

I'm confronted with a situation...

我被要求就Java EE开发之间的方法提出建议。 Spring 3.0和Java EE 6.0。我曾经是，现在仍然是Spring 2.5的推动者，而不是经典的Java EE 5开发，特别是JBoss，我甚至将旧的应用程序迁移到Spring，并影响了这里的开发策略的重新定义，包括Spring特定的API，并帮助了开发一个战略计划来培养更轻量级的解决方案，比如Spring + Tomcat，而不是更重的JBoss，现在，我们只是将JBoss用作Web容器，拥有我称之为容器内容容器的容器，也就是说，拥有大多数API的Spring应用程序在JBoss中运行，所以我们正在迁移到tomcat。

I've been asked to give an advise regarding which approach to take, in terms of Java EE development between Spring 3.0 and Java EE 6.0. I was, and still am, a promoter of Spring 2.5 over classic Java EE 5 development, specially with JBoss, I even migrated old apps to Spring and influenced the re-definition of the development policy here to include Spring specific APIs, and helped the development of a strategic plan to foster more lightweight solutions like Spring + Tomcat, instead of the heavier ones of JBoss, right now, we're using JBoss merely as a Web container, having what I call the "container inside the container paradox", that is, having Spring apps, with most of its APIs, running inside JBoss, So we're in the process of migrating to tomcat.

然而，随着Java EE 6.0的许多功能使Spring在当时具有吸引力，易于部署，耦合较少，甚至某种DI等，似乎已经以某种方式被模仿。 JSF 2.0，JPA 2.0，WebBeans，WebProfiles等。

However, with the coming of Java EE 6.0 many features, that made Spring attractive at that time, easy deployment, less-coupling, even some sort of D.I, etc, seems to have been mimicked, in one way or the other. JSF 2.0, JPA 2.0, WebBeans, WebProfiles, etc.

所以，问题是......

So, the question goes...

从您的角度来看，考虑到Java EE 6.0提供的新视角，继续投资于像Spring这样的非标准Java EE开发框架是多么安全和合乎逻辑？

From your point of view, how safe, and logical, it is to continue to invest in a non-standard Java EE development framework like Spring given the new perspectives offered by Java EE 6.0?

我们可以谈谈Spring开发的3年或4年，或者您是否建议尽早采用Java EE 6.0 API及其实践？

Can we talk about maybe 3 or 4 more years of Spring development, or do you recommend early adoption of Java EE 6.0 APIs and its practices?

I'我会很感激任何见解。

I'll appreciate any insights with this.

推荐答案

关键点恕我直言不是功能之一。在这方面，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.

这篇关于Spring 3.0 vs Java EE 6.0的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！