IE getters/setters for every property in the CFC, or use of setProperty/getProperty methods.
OK, this alone should ring alarm bells... a CFC that implements a getter / setter for every attribute is not encapsulated and therefore is not worth making a CFC out of.
After thinknig on this I'm convincing myself that this is poor use of CFCs, that is, there does not seem to be a compelling reason to use OO stuffs for this.
Correct. If you really find yourself writing code like this, you shouldn't be using CFCs.
There are, likely, ways to implement this using CFCs appropriately but I suspect it will take a substantial rethink of how your application works...
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 word '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]
