I wonder if the JSR 303 bean validation at the client-server-interface is 
really helpful. I stumbled upon two restrictions why I decided to deactivate 
the validation:

   - Beans created within the client might be populated in the back-end. For 
   instance, I have a @NotNull column which contains the creationDate of an 
   entity. It doesn't make sense to let clients set this value, instead it is 
   set just before persisting the first time.
   - Beans object graph needs to be complete for relations with cardinality 
   1 or 1..n. Again a @NotNull association prevents partially filled beans to 
   be send back to the server.

Opinions?

Regards,
Stefan.

-- 
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/-/Bt_UircGSkIJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to