java - Seam with JSF v. Seam with GWT -
would able compare , contrast 2 solutions? don't know seam or jsf, though familiar way gwt works , theory of it.
primary concerns:
scalability / performance
cross-browser compatibility
learning curve
productivity
wysiwyg ui building
capacity code as possible in java (i can touch js/html/css if possible, preferably not)
concerning server-side implementation of app have take following point account (pro/con subjective, should decide) when using gwt instead of jsf.
- as mention @z00bs, using gwt you'll have desktop app. won't use/need page-navigation or page-action feature of seam.
- all requests gwt server short-running. means, of components of
scopetype.event
orscopetype.stateless
, don't need/use conversation scope. - using gwt instead of jsf reduces load on server because hold of state in client.
- you cannot use jsf/seam-lifecycle gwt. instance, lose model validation part in lifecycle. model validation triggered using entity manager or manually
- all other feature, such security, mailing, or el, still working when using seam gwt.
since seam well-known jsf support, should consider framework, such spring roo related gwt, too.
Comments
Post a Comment