The bean in the example I did was actually generated by the RDS plugin of Eclipse. The only validation there is making sure the correct data type is being received (e.g., a number and not a string). The type of validation you are speaking of require some actual <cfif>'s. I would not put that validation in the setter methods, but rather a separate Validation method that can go into the bean.
This way, your cftry around the setters will throw an error if you have bad data types. You could probably handle that by redirecting to the form and populating the form based on what is in the bean. If a particular setter threw an error your getter call should return whatever the default value is. If you don't get an error on any of your setters, then you could run the Validation method that makes sure certain dates make sense, etc. Your validation method could return some sort of message so that you know whether it was all good, or something was bad. If it was bad, you would redirect to the form, populate the form based on the bean's data, and display the message pointing out the invalid data. Hope that helps. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240788 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
