> First, I shared code a while back when CFMX was first released that > showed how to instantiate a CFC using a relative path. This code used > internal CFMX classes, so I am not sure if it still works, but I am > sure that there is a way to do it with CFMX 6.1 even if the code I > shared no longer works
While I personally enjoy messing around with undocumented and unsupported features, I don't think they are a viable solution for my customers... > Maybe cfobject/CreateObject() should support > relative paths for components. That's all I ask, I would be set, I don't need more > 2. Should mappings be configurable on a per application basis? > I would think that would be useful. I also think it would be nice to > separate the paths used for custom tags from that of CFCs. It would be handy, but it's not on top of my list > 3. Should CFCs be fully dynamic? I never felt the need for it. Massimo ---------------------------------------------------------- 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]
