Seam with JSF vs Seam with GWT

Question

Can anyone compare and contrast the two solutions? I don't know much about Seam or JSF, although I am familiar with how GWT works and is very similar to its theory.

Main problems:

• Scalability / performance

• Multi-browser compatible

• Learning curve

• Performance

• Creating the WYSIWYG User Interface

• Ability to code as much as possible in Java (I can touch JS / HTML / CSS if possible, but preferably not)

Answer 1

, : (pro/con , ) GWT JSF.

• @z00bs, GWT , . , / Seam.
• GWT . , ScopeType.EVENT ScopeType.STATELESS, / .
• GWT JSF , .
• JSF/Seam-lifecycle GWT. , .
• , , EL, Seam GWT.

Seam JSF, , ​​ Spring roo, GWT .

Answer 2

, .

GWT :

• java. Java, .
• , java.
• , - . GWT, , ( ).
• . , , .
• Unit Testing GWT MVP .
• UiBinder .

:

• - GWT.
• WYSIWYG GWT Designer ( , , ...)
• GWT , .
• , java.
• ( MVP ).
• , .

, .

( Seam @kraftan).

Answer 3

, Seam, GWT, (, ) .

Answer 4

No! don't use a seam (or jsf for that matter) unless you absolutely need to! There are so many best web technologies in java.