If you want components in various physical locations to inherit from some app-specific classes, where would you put those ancestor classes physically?
The 'extends' property of a component wants a static string, not a variable. So, the paths it sees have to either be in the same directory as the descendant component (not practical for common ancestors to components in many locations), or they have to be full paths. For a full path, if it's from the web root, it breaks if you move the app or deploy somewhere with a different directory structure. If that happens, or you want to guard against the possibility, you could create a mapping whose logical path is the same as the canonical app root you used in your 'extends' properties, pointing to the actual app root. Right? So either your app has to be installed in a specific location relative to the web root, or a specific mapping to where the app actually is has to be created on any server you deploy to. Is this the state of the art, or am I missing something obvious here? Thanks, Dave Merrill ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
