Application.cfm inheritance with CFCs depends on how they're invoked. If you invoke a CFC through Flash Remoting or through the web-service interface (Axis) then Application.cfm is located and run as is the case with any other CF template. However, if you make a call to a CFC from a local CF template then Application.cfm is not processed. This can cause issues if you have your CFCs in a different place from your CFM code and are relying on Application.cfm specific to the CFCs being run.
The way I've worked around this before is I have an Application.cfm for my application and an Application.cfm for my CFC's (which usually share a common cfincluded Application_core.cfm). Within the CFC constructor I check for existence of one of the variables defined in Application.cfm for the CFC's and if it's not there I cfinclude my CFC specific Application.cfm. HTH, Sam ---------------------------------------------- Blog: http://www.rewindlife.com Chart: http://www.blinex.com/products/charting ---------------------------------------------- ---------------------------------------------------------- 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). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
