The documentation talks of removing validation as a concern of the GUI,
by using object validation that gets done before any commits. However,
validation can continue to be needed in the GUI since it is always nicer
to let users know of problems early on (such as the maximum length of a
value, that a value must be a number or a value must not be null, as
well as business validation). Is there some way to have database
constraints visible to the GUI developer, perhaps through use of the
class generation templates (by adding constraints as constants in the
superclass, for example)?
Thanks,
Tony
This archive was generated by hypermail 2.0.0 : Mon Apr 13 2009 - 19:26:56 EDT