Consider the responsibilities... Is it the responsibility of the user to know the password? Yes. Is it the responsibility of the user to validate the password? Probably not. I would lean toward having a separate password object as previously suggested. Maybe it would be rolled-up into an authentication object that handles all authentication and password tasks. Mike
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Alan Livie Sent: Monday, October 20, 2008 7:27 AM To: [email protected] Subject: [CFCDEV] Re: User password changes and OO confusion New password twice as in the form it asks for 'new password' and 'confirm new password'. One of the validation checks is that 'new password' equals the 'confirm new password' value. I could go down the route of another service but I'm trying hard to avoid going in the direction of an 'anemic domain model' with fat services and thin business objects. This is why I'm keen to get this logic into User where I think it probably belongs. I'm going with John's earlier suggestion in the meantime and see where it gets me. As the saying goes there are many ways to skin the cat! Alan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
