>>I would generally expect TOs to be effectively read only - an init() method and getters (but no setters). I'd be suspicious of code that wanted to create a fully populated TO and then mess with its data...
I think I'm getting more and more confused with the difference between beans and transfer objects. I have a CFC, which I call a bean (maybe I'm wrong), that has setters and getters and validation logic. This is the one where all the setters are string data types. Are you saying that once I have the bean fully-populated, I should then pass that into a transfer object as a whole, where the transfer object then *only* returns data that was passed to it? If so, am I wrong in passing a bean directly into a DAO? Such as: Good: Bean --> Transfer Object --> Data Access Object Evil: Bean --> Data Access Object Maybe I'm just confused on terminology. Thanks MAD ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
