Peter Bell just posted an article on the possibility of doing dynamic extension of components. Most frameworks, as you know, require the base code to be installed in a "known" location (e.g. /reactor or /coldspring), since the component extends attribute can't be or contain a variable. As in:
<component extends="#base#.something.object" ...
But if you "had" to do this, one way might be to do so using auto-generated code in "reactor"-type fashion.
Let's say you have a base framework "B", and your customized code "C", which normally extends "B", but "B" could be anywhere.
To combat that let's say that there's a a factory "F", and set of generated classes, "G", such that "C" extends "G", which extends "B".
You ask the factory for an object based on your custom class "C". The factory tries to create it, and fails because the "G" class is missing or points to the wrong location. The factory then generates the "G" "stub" class file based on some configuration value so it points to the current location of "B", and then attempts to instantiate "C" again.
Since "C" extends "G", which now points to the correct location of "B", everything works.
All in all, I think I'd prefer this type of intermediate class approach as opposed to an attempt to correctly read, parse, and rewrite a user's cfc to "extend" properly.
Comments