The other use of CFPROPERTY is to populate the meta data of a component.
...
Unfortunately, use of meta data that way is often unacceptable from a
performance/scaling standpoint.
I'll second this (as Nathan well knows, based on the aforementioned CMS to which I contributed mostly critique :)
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.
Agreed. Don't worry about CFPROPERTY unless you're trying to build complex web services and you actually *need* its validation.
As my coding guidelines say:
http://www.corfield.org/coldfusion/coding_standards/goodpractice.html
"Components & cfproperty
Be aware that the cfproperty tag is of limited use - it does only two things:
� It provides additional type validation for Web Service return types.
� It provides a way to add metadata to components.
In general, cfproperty should not be used - it does not provide type checking for instance data (in general) and it does not provide default values for instance data so its presence can be misleading rather than helpful.
If you really are returning a component type from a Web Service and want the public data members of that component to be type-checked at runtime, then cfproperty can be useful.
If you are creating a metadata-driven system, then cfproperty can be useful (although dynamic systems driven by component metadata tend not to scale well!)."
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]
