The idea is :
"Since GWT is rigid in "when things should happen" (phases), it should be more permissive in how you manage each step"
Since it imposes that validation must happen only the validation phase, it should allow to better tune how you do your validation.
Don't get me wrong, it's a very great thing that GWT's RF imposes an architecture, this is suited for bigger teams and allows a faster understanding of any GWT solution for newcomers on a project. but therefore it become an enterprise solution that has to provide some enterprise services. It comes to my mind that RF is for GWT what JEE is for Spring (or for raw java). Since in Jee each EJB has its own rules and restrictions, enough stuff to cover the needs in the restricted world of each ejb must be provided (too much restriction makes the architecture unusable)
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.