Since i can not change the way CF works i'll have to do with its limitations as well, but a flat directory is no option for me. We have a team of cf developers working on various applications, creating their own cfc's (if they cant extend one of the common), which they want to give proper names, inevitably they will come up with duplicate names sooner or later. On a sidenote DO notice that you CAN extend from the common package to the application-specific package. If there really is a need to extend something cross-application package, they'll have to give me a real good reason for it, and 'll include the cfc in the common lib, but i force them to make it as generic as possible before i accept it and as i already said before, it rarely happens. The original question was how other people do it. This is how we do it, and it works for us. Don't focus too hard on things that don't work.
Cheers, Stijn. ---------------------------------------------------------- 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]
