Re: GWT vs SmartGWT

I recommend straight GWT for almost everything. The other frameworks just add abstractions on top of GWT that confuse things a lot more.

Designing screens: UI Binder

Client-side validation: Editor framework + JSR303 validation using HibernateValidator 4.0.2GA

Performance: AsyncProxy, ClientBundle, stick to concrete collections in data transfer objects, etc

Communicate with server over WSDL: you are kind of fucked on this one. I don't know why you would want your javascript to talk WSDL with a server. While I appreciate SOAP/WSDL, that is just way too much overhead for your javascript client to deal with. Your server's WSDL layer likely uses some sort of business interface written in Java. Create a new backend endpoint using REST or for even easier GWT-integration using GWT-RPC. This endpoint should just reuse the same business interface that your WSDL endpoint uses.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/LewlhrMuFccJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.