To build on what Ray said... Assuming a file named myTag.cfm in the same directory, all four of these are identical in functionality; they differ only in syntax:
<cfimport prefix="t" taglib="." /> <t:myTag ... /> <cfmodule template="myTag.cfm" ... /> <cfmodule name="myTag" ... /> <cf_myTag ... /> One of the benefits of CFIMPORT is that you can define a specific location that you want to look for a tag definition, rather than scanning the local directory and then the entire custom tag tree. That lets you have multiple versions of your custom tags on a single server, and always reference the correct one. You can also use CF mappings in your TAGLIB attribute, though if you ever change the mapping, make sure you delete the class files and bounce CF. This lets you avoid all the nasty relative pathing crap that you need if you're using CFMODULE, and lets you pinpoint a specific directory for the tags, rather than the directory scan. This makes CFIMPORT ridiculously powerful compared to CFMODULE and the CF_ syntax. I usually set up a mapping to a directory for each application, and then put various tag libraries under that directory in subdirectories. That gives something akin to CFC packages, except with custom tags. Works very well, i think. cheers, barneyb On Fri, 06 Aug 2004 12:32:30 -0500, Raymond Camden <[EMAIL PROTECTED]> wrote: > Calling a tag via cfimport (well, using the scope created by using > cfimport) acts like a custom tag call - ie there is a separation of scopes. > > -Ray > ---------------------------------------------------------- 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]
