In an ideal application nothing would ever call a getter or setter. Unfortunately, in reality this is pretty much impossible; data has to get into an object somehow, and it has to be displayed somehow.
In good OO design, objects TELL other objects what to do, they don't ASK other objects for their internal data. This is the basis of the design principle "Tell, don't ask". On Mon, Sep 1, 2008 at 4:44 AM, Alan Livie <[EMAIL PROTECTED]>wrote: > > Fat beans - thin(ish) services. > > Alan > ________________________________________ > From: [email protected] [EMAIL PROTECTED] On Behalf Of Henry > [EMAIL PROTECTED] > Sent: 28 August 2008 04:01 > To: CFCDev > Subject: [CFCDEV] fat bean vs fat service? > > I wonder what's prefered... should the bean methods work with > properties of a bean, or should the service methods do everything to a > bean, by calling all the getters and setters? > > What do you use? > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
