I'd be careful doing this. For certain things there is no way around making a dynamic call. But if you add lots of calls to dynamic CFC names, with dynamic method names and dynamic arguments, you're basically making it impossible to follow the application flow and probably making things very difficult to test. Also, if any of these variables are coming from the form or URL scope, it opens up huge security holes because the user could modify the values and essentially be able to call anything.
On 9/7/07, Josh Nathanson <[EMAIL PROTECTED]> wrote: > > > You don't have to get that complex. Just do > > > > <cfinvoke component="#application.aImage#" method="#method#"> > > I think he said the component name was dynamic as well as the method > though, > so he'd need to do this: > > <cfinvoke component="#application[componentname]#" method="#method#"> > > -- Josh > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion 8 - Build next generation apps today, with easy PDF and Ajax features - download now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:287988 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
