That sounds interesting, yes. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gurevich, Gerry (NIH/NIEHS) [C] Sent: Friday, January 20, 2006 8:38 PM To: [email protected] Subject: RE: [CFCDev] Bean and CFC question
I posted something about this earlier in the thread, but it seems to have gotten lost in the noise. I use <cfproperty> to set up the names and types of properties. I also use it to indicate required fields. Then I use that metadata to perform inserts and updates using the data types. I've had very good results, it preserves the integrity of the hidden INSTANCE scope and it produces very usable, readable, and extensible code. ----------------------------------- Gerry Gurevich Application Development NIEHS ITSS Contractor Lockheed Martin Information Technology 919-361-5444 ext 311 -----Original Message----- From: Sean Corfield [mailto:[EMAIL PROTECTED] Sent: Friday, January 20, 2006 7:49 PM To: [email protected] Subject: Re: [CFCDev] Bean and CFC question On 1/20/06, Joe Rinehart <[EMAIL PROTECTED]> wrote: > Ugh, I'm still against it. It allows (at least a portion of) your > CFC's private scope to be manipulated directly, essentially tossing > out the whole of data hiding. Well, strictly speaking, since you're simulating a *public* getter / setter, you're not really manipulating the private scope directly. However, there does need to be a safeguard in place. How about <cfproperty>? You could use <cfproperty> to declare the properties that could be manipulated with the generic get() / set() methods and have them check the metadata... (Yes, in the past I've railed against metadata-driven systems - I'm only offering this as a "standard" way to document the (effectively public) properties that should be available to the get/set methods) -- Sean A Corfield -- http://corfield.org/ Got frameworks? "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' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
