> > I saw Ray mentioned the possibility of inheriting the > auditTrail CFC in > > the department CFC. That is probably not an OO solution, since a > > "department" is not an "auditTrail". This would be an is-a > relationship, > > and is usually implemented using inheritance. > > Makes sense.
Just want to ditto the earlier comment - it does _not_ make sense to make Department inherit auditTrail - so just ignore me when I say crap like that. ;) > > A department has an audit trail, though. This is a has-a > relationship, > > which is usually implemented using properties. You could > make a property > > with the type being "auditTrail". However, I am unclear as > to how you > > would access methods of "auditTrail" via the property of > department. ( if > > that makes sense). > > Hmm. Sounds like a possibility, but since I've not run > across any articles > pertaining to the use of component properties (or if I have I You should look into CFC properties some - they are an interesting concept and add an extra layer of functionality to your CFCs. What's interesting is that you can have both 'private' and public (This) data in your CFCs. ======================================================================= Raymond Camden, ColdFusion Jedi Master for Macromedia Email : [EMAIL PROTECTED] Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
