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

查看:113
本文介绍了Java EE 6与Spring 3堆栈的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

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

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).


另一方面,我需要JPA(Hibernate或替代)和JSF与IceFaces。

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配置文件。

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)上的代码,而不是专有容器(Spring)上的代码。我认为Java EE 6已经足够好了(这是一个委婉语,EJB 3.1(Lite),JPA 2.0,JSF 2.0,CDI kick ass)。请注意,我是一个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屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆