I do want to use a persisted CFC....but I want to use it on the spot, in the CFGRID tag. I don't want to:
1) Do exactly what you stated is generally recommended against. I don't want to be accessing a shared scope directly in a CFC. I've taught others not to do it, and I'm not going to do it either. 2) I already have a perfectly good CFC that does everything I need it to do, but I can't use it because I can't instantiate it properly. It's not a static CFC. I don't want to have to write another CFC with the sole purpose of accessing a variable that does everything I need if I don't have to. I know what my options are, but you're not answering my question, which is simply this. Is there any way I can use a variable in the bind attribute instead of a path to a CFC? >So I'm confused - are you saying the only reason you don't want to use >a persisted CFC is.... what? Why isn't this CFC (myPeeps) cached in >the app scope? You could then make another CFC, just for AJAX >purposes, that works with this app scoped CFC. I know that - in >general - folks recommend against that, but for AJAX I think it makes >sense. The CFC is simply acting as a proxy to your cached components. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:317571 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
