Java – seam using JSF and seam using GWT

Can anyone compare and contrast these two solutions? I know little about seam or JSF, although I am familiar with the way GWT works and like its theory very much

Main concerns:

>Scalability / performance > cross browser compatibility > learning curve > productivity > WYSIWYG UI building > capacity to write as much code as possible in Java (if possible, I can touch JS / HTML / CSS, but it's best not)

Solution

As for the server-side implementation of the application, when using GWT instead of JSF, you must consider the following points (Pro / con is subjective, so you should decide)

>As @ z00bs mentioned, you will have an app like desktop using GWT Therefore, you will not use / need seam's page navigation or page manipulation functions. > All requests from GWT to the server are short - running This means that most of your components are scopetype Event or scopetype Status, and you don't need / use session scope. > Using GWT instead of JSF can reduce the load on the server because you occupy most of the state on the client. > You cannot use the JSF / seam lifecycle with GWT For example, you lose the model validation part of the lifecycle Model validation can only be done by using entity manager or manually triggering > when using seam and GWT, all other functions (such as security, mail or EL) are still valid

Since seam is known for its JSF support, you should consider another framework, such as spring Roo, which is closely related to GWT