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.
Primary concerns:
Scalability / performance
Cross-browser compatibility
Learning curve
Productivity
WYSIWYG UI building
Capacity to code as much as possible in Java (I can touch JS/HTML/CSS if possible, but preferably not)
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:
To your main concerns:
Hope that helps.
(Some considerations concerning the choice of Seam are coming soon from @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.
ScopeType.EVENT
or ScopeType.STATELESS
and you don't need/use the conversation scope. 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提供的会话范围可以很容易地在GWT中替换。
Neither! dont use seam (or jsf for that matter) if you absolutely dont have to! There are so many better web techs on java.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.