JSF和Spring性能与差的JSP性能 [英] JSF and Spring performance vs poor JSP performance

问题描述

我看到我的同事开发的一些JSF项目，这些项目在我看来很慢。有人有同样的看法吗？

I saw some JSF projects developed by my collegues and these projects seemed to me very slow. Does anybody have the same opinion?

我目前使用jsp + jstl和jQuery forrich客户端。

I'm currently using jsp+jstl and jQuery for "rich" client.

我不知道现代框架（jsf，wicket，tapestry ..）在旧的普通jsp上有什么优点和缺点。

I wonder what advantages and disadvantages have modern frameworks (jsf, wicket, tapestry..) over old plain jsp.

如果使用所有这些技术的人都回答了，那将是非常好的。

It would be great if people who used all these technologies had answered.

最令人兴奋的功能使你离开jsp和使用大规模框架（我的意思，例如AOP在Spring或其他任何你可以注意到的）。

It's also interesting for me which most exciting features made you to leave jsp and use "massive" framework (I mean, for example AOP in Spring or something else whatever you can notice).

感谢所有评论。

推荐答案

，PHP，JSP，Struts，Spring MVC（1.2），Bea工作室，JSF，JBoss Seam，Spring MVC（2.5）和 Wicket （按此顺序）。我注意到我在工作的每种新技术的生产力和质量的跳跃。它只是工作更好，它感觉更好。我喜欢Wicket（与春天，石英等扭曲）在所有其他。我可以诚实地说，我看到了光，我不想回到一个更黑的 - 或更轻;） - 侧。

I've used CGI, PHP, JSP, Struts, Spring MVC (1.2), Bea workshop, JSF, JBoss Seam, Spring MVC (2.5) and Wicket (in that order). I've noticed a jump in both productivity and quality for each new technology I've worked on. It just works better, It feels better. I prefer Wicket (with a twist of spring, quartz, etc.) over all of the others. I can honestly say I saw the light, and I don't want to go back to a darker -- or lighter ;) -- side.

有很多

• 默认情况下，会话支持（或启用Tab）功能不需要担心在新标签页中打开


• 它是基于组件的，因此您可以重复使用代码ala swing。




• 支持高级安全功能，如url加密。


• 默认情况下可集群化应用程序。


• 最重要的是有趣。

• Conversational support (or tab-enabling) comes by default, you do not worry about "open in a new tab" and "back" button problems ever again.
• It is component-based, so you can re-use code ala swing.
• Leverages a lot of the standard Java, like the type safety wonders.
• Supports advanced security features like url encryption.
• Clusterizable applications by default.
• And, most important, it is fun to use.

• 最让我困扰的是EL废话，因为我相信


• 两者都需要工具支持，以提高生产力。


• 您需要另一个框架（如使用seam框架，这使得JSF可用）。


• 错误处理是非常棘手的，并且异常不能直截了当。


• 很难在两个框架上创建可重用的组件，也不支持分离关注点的正确模型。


• ...最重要的是，轻微痛苦，如这，或 this 。

• The one thing that bothers me the most is the "EL" nonsense, for I believe it breaks the nice java type safety and strength.
• Both need tooling support for high productivity.
• You need another framework on top of both of them to really solve the problems (as seen with seam framework, which makes JSF usable).
• The error handling is very tricky and the exceptions are not straitforward helpful.
• It is difficult to make reusable components on both frameworks and doesn't support a proper model for separation of concerns.
• ... and, most important, a long etc of minor pains, like this, or this.

这篇关于JSF和Spring性能与差的JSP性能的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！