> While cfproperty values exist in metadata, they do not create > real values. Ie, <cfproperty name="name" value="ray"> will > create data in the metadata, NOT in the This scope or unnamed > scope. Basically, don't make the mistake of thinking > <cfproperty> creates 'real' values.
So what is the point of the cfproperty tag? What is the point of metadata? And how do you use the data that is created using cfproperty?
There isn't one if you don't use web services. This tag only serves to create metadata about the CFC to external systems (non-CF). Although, to be honest, I'm not really sure what the external systems do with it. Maybe others can clarify that. Personally, I think the cfproperty name is the most egregious of the poorly named tags, as it has caused lots of confusion, yours being only the latest in a long line (me included at first).
I would, but, I think it's easier to create re-usable code if you don't use 2 completely different languages to do one thing. I want to use CFC's, so let's start using them properly!
I don't get what you mean by "2 completely different languages". CFCs still use the standard CFML library, albeit with a couple of the new tags introduced in MX. Can you explain further?
> Just curious - but where are you seeing bad examples of CFCs? > While this list is active, I'm not seeing CFCs used a lot in > the 'wild'. CFCZone has gotten 2-3 submissions, but not > nearly as much response as CFLib did when CF5 was released.
It's more that people who start to use CFC's use them wrong (and I mean obviously wrong). Treat them like function libraries and not components (I'm not going to use the word objects here!). I do think that MACR has missed out on explaining them properly and using them properly in code. Most people still do CF5 style coding and don't use CFC's to their potential.
Oh, I don't know about that. CFCs are way more than "function libraries." CFCs are also a logical place to organize and store business rules as well, which I think is their true power. Have you read through the "Developing ColdFusion MX Applications with CFML" book MM provides with MX? You really should if you haven't, as it's an *excellent* primer on CFCs. I also highly recommend the "ColdFusion MX Bible" by Adam Churvis et al. It's really the only book where I've seen CFCs cleanly explained with all their caveats (i.e., locking within persistent CFCs, etc.).
I haven't seen CFC's used much in the wild (in the minor Open Source projects I've seen...), but it strikes me that we need a list like this and more resources to begin to use them properly!
The Design Patterns article in CFDJ was very interesting, probably most interesting to me was the "hack" at creating an abstract method (function) by putting a <cfabort> in the function... Beginning to get a better idea of how I can use them!
Excuse me if I'm parsing your sentence too anally, but you say "article" when in fact there has been a series of articles by Brendan O'Hara in the CFDJ using different design patterns. Have you had a chance to read through all of them? They're pretty good.
Regards, Dave.
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
----------------------------------------------------------
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).
