[英]Seam with JSF v. Seam with GWT
Would anyone be able to compare and contrast the two solutions? 有人能比较和对比这两种解决方案吗? I don't know much about Seam or JSF, though I am familiar with the way GWT works and very much like the theory of it. 我对Seam或JSF知之甚少,虽然我熟悉GWT的工作方式,非常喜欢它的理论。
Primary concerns: 主要关注点:
Scalability / performance 可扩展性/性能
Cross-browser compatibility 跨浏览器兼容性
Learning curve 学习曲线
Productivity 生产率
WYSIWYG UI building WYSIWYG UI构建
Capacity to code as much as possible in Java (I can touch JS/HTML/CSS if possible, but preferably not) 在Java中尽可能多地编码的能力(如果可能,我可以触摸JS / HTML / CSS,但最好不要)
Concerning the client-side development of your app we had the same decision to make. 关于您的应用程序的客户端开发,我们做出了同样的决定。
We decided to go for GWT for the following reasons: 我们决定选择GWT,理由如下:
To your main concerns: 对您主要关注的问题:
Hope that helps. 希望有所帮助。
(Some considerations concerning the choice of Seam are coming soon from @kraftan). (有关Seam选择的一些考虑因素很快将来自@kraftan)。
Concerning the server-side implementation of your app you have to take the following point into account (pro/con is subjective, so you should decide) when using GWT instead of JSF. 关于应用程序的服务器端实现,在使用GWT而不是JSF时,必须考虑以下几点(pro / con是主观的,所以你应该决定)。
ScopeType.EVENT
or ScopeType.STATELESS
and you don't need/use the conversation scope. 这意味着,您的大多数组件都是ScopeType.EVENT
或ScopeType.STATELESS
并且您不需要/使用会话范围。 Since Seam is well-known for its JSF support, you should consider another framework, such as Spring roo which is strongly related to GWT, too. 由于Seam以其JSF支持而闻名,因此您应该考虑另一个框架,例如与GWT密切相关的Spring roo 。
通过在客户端的内存中存储长期持续交易(如购物车),Seam提供的会话范围可以很容易地在GWT中替换。
Neither! 都不是! dont use seam (or jsf for that matter) if you absolutely dont have to! 如果你绝对没有必要,请不要使用seam(或者jsf)! There are so many better web techs on java. java上有很多更好的Web技术。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.