Java EE 6 与 Spring 3 堆栈 [英] Java EE 6 vs. Spring 3 stack

问题描述

我现在开始一个新项目.我必须选择技术.我需要一些简单的东西，所以没有 EJB 或 Seam.另一方面，我需要带有 IceFaces 的 JPA(Hibernate 或替代)和 JSF.

I'm starting a new project now. I have to choose technologies. I need something light, so no EJB or Seam. On the other hand I need JPA (Hibernate or alternative) and JSF with IceFaces.

你认为部署在Tomcat上的Spring 3上这样的栈是一个不错的选择吗?或者 Java EE 6 Web 应用程序会更好吗?恐怕 Java EE 6 是一项新技术，尚未得到很好的记录.Tomcat 似乎比 Glassfish 3 更容易维护.

Do you think that such a stack on Spring 3 deployed on Tomcat is a good choice? Or a Java EE 6 web application could be better? I'm afraid that Java EE 6 is a new technology, not well documented yet. Tomcat seems to be easier to maintain than Glassfish 3.

你有什么看法?你有什么经验吗?

What's your opinion? Do you have any experiences?

推荐答案

我需要一些简单的东西，所以没有 EJB 或 Seam.

I need something light, so no EJB or Seam.

您是否愿意解释自 EJB3 以来是什么使 EJB 变得沉重?你有没有意识到我们已经不是 2004 年了?我真的很想阅读你对光的定义和你的论点(我会很高兴地更新我的答案，因为我很确定我会有一些可靠的话要说).

Would you care to explain what makes EJBs heavy since EJB3? Do you realize that we are not in 2004 anymore? I'd really like to read your definition of light and your arguments (and I will update my answer with pleasure because I'm pretty sure I would have a few solid things to say).

另一方面，我需要带有 IceFaces 的 JPA(Hibernate 或替代)和 JSF.

On the other hand I need JPA (Hibernate or alternative) and JSF with IceFaces.

Java EE 6 Web Profile，其中包括 JSF 2.0、JPA 2.0、Bean Validation、EJB 3.1 Lite、CDI ……非常适合这个，您可以使用 GlassFish v3 Web Profile 以运行使用 Java EE 6 Web Profile 构建的应用程序.

Java EE 6 Web Profile which includes JSF 2.0, JPA 2.0, Bean Validation, EJB 3.1 Lite, CDI,... would be perfect for this and you can use GlassFish v3 Web Profile to run an application built with the Java EE 6 Web Profile.

您认为部署在Tomcat上的Spring 3上的这种堆栈是一个不错的选择吗?或者 Java EE 6 Web 应用程序会更好吗?

Do you think that such stack on Spring 3 deployed on Tomcat is a good choice? Or a Java EE 6 web application could be better?

好吧，我喜欢在非专有平台(Java EE)而不是在专有容器上运行我的代码的想法(春天).而且我认为 Java EE 6 已经足够好了(这是委婉的说法，EJB 3.1 (Lite)、JPA 2.0、JSF 2.0、CDI 踢屁股).请注意，我对 JSF 持怀疑态度，但我又看了一眼，发现带有 CDI 的 JSF 2.0 是如此不同，我什至无法进行比较.如果你不看 CDI，让我告诉你它很酷.

Well, I like the idea to run my code on a non-proprietary platform (Java EE) rather than on a proprietary container (Spring). And I think that Java EE 6 is good enough (and this is an euphemism, EJB 3.1 (Lite), JPA 2.0, JSF 2.0, CDI kick ass). Note that I was a JSF skeptic but I took a second look and JSF 2.0 with CDI is so different that I can't even compare. And if you didn't look at CDI, let me tell you that it rocks.

我担心 Java EE 6 是一项新技术，还没有很好的文档记录.

I'm afraid that Java EE 6 is a new technology, not well documented yet.

Java EE 对我来说似乎有很好的文档记录.这听起来像是免费索赔.而且，不管你信不信，我开始发现 Spring 越来越复杂，而 Java EE 越来越容易.

Java EE looks pretty well documented to me. This sounds like free claim. And, believe me or not, I start to find Spring getting complicated while Java EE getting easier.

Tomcat 似乎比 Glassfish 3 更容易维护.

Tomcat seems to be easier to maintain than Glassfish 3.

你尝试过吗?你遇到过什么特别的问题吗?同样，这听起来像是免费声明.

Did you try something? Did you face any particular problem? Again, this sounds like free claim.

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