> But if the decision is that PhotoArticles ARE different enough to be new > objects, my take would still be using the manager to handle the > relationship between the BO's and the DAO/Gateways.
I totally agree... relationships between different architectural layers (domain, persistence, etc) should be handled by the manager. I'm also suggesting that relationships and business rules between business object be solely handled by the business objects themselves. > Polymorphism would be an aid in this case. > > Say you have a BlogContentManager. And say you have an abstract class > called BlogContent, which is subclassed by BlogArticle and BlogPhoto > (and any future types of blog content). If we decide on a standard > interface for all of the subclasses of BlogContent, then the > BlogContentManager would only need to deal with the BlogContent objects. > It would never know whether any given object was actually a BlogArticle > or a BlogPhoto. Word ---------------------------------------------------------- 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]
