This stands to reason, as the grid objects needs to know if the relevant JS has been included once already, in case you have multiple grids on a page (or any other controls using the same JS files). It seems that calling multiple grid tags reuses the same java object in a page (and in this case it's stored in the CFC instance).
On 9/11/07, Charles Sheehan-Miles <[EMAIL PROTECTED]> wrote: > Well, the verdict here: > > 1) If I create the object every request, the javascript appears and > the cfform works fine > 2) If I CFINCLUDE a CFM template, the javascript appears and the > cffform works fine > 3) If it is invoked from a persistent object (in either application > or session scope) it shows up the first time I access the page, but > subsequent access fails to send the page with the needed javascript > > Hmm. I want the cfgrid considerably less than I want to do either of > the first two, because both of the first two options introduce the > problems I was trying to avoid by having the thing in memory in the > first place. Ah, well. -- mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion is delivering applications solutions at at top companies around the world in government. Find out how and where now http://www.adobe.com/cfusion/showcase/index.cfm?event=finder&productID=1522&loc=en_us Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288133 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
