I have been leaning towards putting my validation (I am new at this) inside of the DAO object. The DAO validate would accept some sort of entity bean and then return a validation error collection object:
UserDAO.Validate(User) - > Returns instance of extensions.components.ValidationErrorCollection Of course this is just theory for me at the moment, but what I like about it is that validation can happen in an organized format at the programmer's request. Plus, getting a standard collection interface is good for outputting the form errors to the end user. ....................... Ben Nadel Web Developer Nylon Technology 6 West 14th Street New York, NY 10011 212.691.1134 212.691.3477 fax www.nylontechnology.com "Vote for Pedro" -----Original Message----- From: Michael Dinowitz [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 07, 2005 10:48 AM To: CF-Talk Subject: Re: CFC design - data validation? Have a method called setemailaddress() that calls another method that validates the email address. If it validates, then save otherwise return an error message. My listserver CFC does this (among other things). One of the powers of CFCs is the ability to have clean organization of code. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:226439 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
