We have a couple different approaches. But one is to create some custom validator Fields that can be plugged in to the validator. Then all errors, buisiness or otherwise, are done by the DynaValidatorForm.
Makes our actions simpler. -Dennis On Fri, 2003-03-14 at 14:47, Dan Allen wrote: > *This message was transferred with a trial version of CommuniGate(tm) Pro* > Naturally all screening of data should be done by the > ActionForm/Validator interface, but when it comes time to looking > for duplicate usernames/emails or other such business conflicts, > this must be done in the business logic layer. > > How do most of you handle this? Do you create a validateData() > method in your Action class or is this something that the Model > objects should be able to handle? > > Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
