So I'm still a little foggy on just what a BO does. Besides functions for
validation, does it do anything else?
Answer: it depends. In simple systems, business objects don't do much because there just isn't much business logic in the system as a whole. That's also the trouble with looking at small sample applications - they're simply not complex enough to show either why you would partition the application nor really what the function of each part of the application plays.
There are also cases where the business object is constantly being updated and is also persistent. In such cases, it can be simpler to merge the BO and its DAO since it is essentially its own manager, i.e., it knows when an operation causes changes that need to be persisted.
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
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]
