I was thinking of something like that- using metadata that is. Like
<cfcomponent implements='net.temm.hierarchicalDataClass'>
...
Sound like a viable path? Sean, do you have that BACFUG presentation lying around somewhere?
I presented it at a BACFUG panel in 2002 - download all of the presented material (myself, Matt Liotta and Nathan Dintenfass I believe) from:
http://www.bacfug.net/code.cfm
CFMX_Panel_Discussion.zip from 8/6/2002 - my section is the CFCMetaData.zip files which includes the implements= example.
It was a theoretical experiment and not something I'd necessarily recommend in real code. The primary benefit of interfaces in Java is being able to specify interface types in arguments and have the compiler validate it - that benefit is not possible in CFMX because you have to specify a generic "component" type :(
Sean A Corfield -- http://www.corfield.org/blog/
"The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man."
-- George Bernard Shaw
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words '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]
