You could probably jimmy-rig something with throwing an error, catching it, and then exacmining the stack trace to ensure that the "certain CFC" is in there. However, that's probably a lot more work than it's worth. Or perhaps the function for examining your tag context within a custom tag would work in a similar way?
Cheers, barneyb > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bryan F. Hogan > Sent: Thursday, January 15, 2004 12:49 PM > To: [EMAIL PROTECTED] Org > Subject: [CFCDev] Making sure is not called out of sequence > > Does anyone know if it is possible to make sure that a CFC is > not called > directly and that can only be called from a certain CFC when the CFC > that shouldn't be called is in a sub-directory of the CFC > that should be > the only caller? > > > ---------------------------------------------------------- > 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] > ---------------------------------------------------------- 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]
