J MacKay wrote:
*/Jim Cassata
/*
well if the cfc is in the current directory as the calling
template you just need the cfc name. As I understand it, CF will
look for your cfc in the following order:
1) current directory of the calling cfml page
2) mapped coldfusion paths
3) custom tag directories
So keep that in mind for portability concerns
HTH
Jim,
Yes, but I want to organize my cfcs into different folders. Which
means I either skip typing or am required include the full path
whenever I reference a component in a different package.
Janet
------------------------------------------------------------------------
I would be tempted to "name" the packages by creating a mapping for each
one. Then you can access them relatively easily and add a little
self-documentation in the process:
... extends="/PackageA/cfc1" ...
... returns="/PackageA/cfc1" ...
etc.
Does that work?
Aaron
You are subscribed to cfcdev. To unsubscribe, please follow the instructions at
http://www.cfczone.org/listserv.cfm
CFCDev is supported by:
Katapult Media, Inc.
We are cool code geeks looking for fun projects to rock!
www.katapultmedia.com
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
