You could try dumping the variables scope of the CFC to see if cfform is putting something in there. But whatever the problem is, I'm pretty sure it must be related to the fact that the CFC is being stored in a shared scope. Does switching to a per-request CFC allow the JavaScript to work correctly? While I don't recommend doing it in general, you might also see if doing a cfinclude of a template that contains the cfform tags makes a difference.
On 9/10/07, Jaime Metcher <[EMAIL PROTECTED]> wrote: > > Well, this really is just a wild guess, but maybe it's worth trying > re-instantiating the CFC on every request. CFFORM could be stashing some > state in that CFC. > > Jaime Metcher > > > -----Original Message----- > > From: Charles Sheehan-Miles [mailto:[EMAIL PROTECTED] > > Sent: Monday, 10 September 2007 6:58 PM > > To: CF-Talk > > Subject: Re: Odd behavior when using cfform inside a CFC > > > > > > Jaime .... interesting question, and yes, the CFC in this case is > > stored in the session scope. > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Check out the new features and enhancements in the latest product release - download the "What's New PDF" now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288093 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
