They are totally unrelated and not interchangeable. CFPROPERTY has one primary use -- helping to define complex return types in web services. See the CF documentation on web services and CFPROPERTY for examples of that.
The other use of CFPROPERTY is to populate the meta data of a component. In most cases, that is not really that useful, though some application use meta data to do abstract "interesting things". For instance, I once built a prototype CMS in which you could extend a baseContentObject and use CFPROPERTY to define the various "fields" of your data object. Unfortunately, use of meta data that way is often unacceptable from a performance/scaling standpoint. If you are just getting started with components (or are doing some deep web services development) I would just ignore CFPROPERTY -- it tends to confuse people more than it actually is useful. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Ian Skinner > Sent: Tuesday, September 23, 2003 1:00 PM > To: CfCdevzone (E-mail) > Subject: [CFCDev] <CFPROPERTY> WAS Using a CFC as the action of a form. > > > Looking through the link > {http://www.benorama.com/coldfusion/patterns/part2.htm}, I > learned of a new > tag. <CFPROPERTY...>. A quick lookup in the documentation gave me a vague > idea of what this tag does, but not really enough to understand it. What > are the differences between <cfproperty...> and <cfargument...>? When is > one better to use then the other? > ---------------------------------------------------------- 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]
