Thanks, Robert. That looks like a good plan. Tony
-----Original Message----- From: Robert Zeigler [mailto:[email protected]] Sent: Tuesday, 14 April 2009 11:38 a.m. To: [email protected] Subject: Re: Validation Constraint information is available by examining the ObjEntity and DbEntity objects corresponding to the given object class. I used this in the tapestry5-cayenne integration module (t5cayenne) to have tapestry automatically pick up the relevant data constraints Note: currently, t5cayenne supports the required constraint for any field type, the maxlength constraint for only string types, and no other constraints. This is due to what I was interested in supporting at the time I wrote it rather than to some fundamental limitation; any remaining constraints will likely be added at some point in the future. All of those caveats notwithstanding, you can take a look at the code for ideas: http://code.google.com/p/tapestry5-cayenne/source/browse/trunk/tapestry5 -cayenne-core/src/main/java/com/googlecode/tapestry5cayenne/services/Cay enneConstraintGenerator.java Robert NOTICE - This message and any attached files may contain information that is confidential, legally privileged or proprietary. It is intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error. Any dissemination, copying, use or re-transmission of this message or attachment, or the disclosure of any information therein, is strictly forbidden. BlueScope Steel Limited does not represent or guarantee that this message or attachment is free of errors, virus or interference. If you have received this message in error please notify the sender immediately and delete the message. Any views expressed in this email are not necessarily the views of BlueScope Steel Limited.
