Comments on: CF 8 Ajax with CFSELECT BIND

By: Ross

Ross — Fri, 08 Oct 2010 20:31:08 +0000

You don’t need to remove the entire onRequestStart method. I initially ran into problems with Ben’s example because my onRequestStart and End methods were including my header and footer HTML. Changing my code to this allowed the bind to work:

By: Chris

Chris — Sat, 28 Mar 2009 18:54:32 +0000

You can deal with this dynamically at runtime, and still keep onRequest for cfm pages:
[coldfusion]

[/coldfusion]

By: John C. Bland II

John C. Bland II — Sat, 28 Mar 2009 18:53:24 +0000

Matt, as you pointed to Ben's quote, the onRequest method is problematic for web services, Flash Remoting, etc. The problem is you are trying to call "whatever.cfc" and onRequest is attempting to serve the file to the browser vs allow a direct call to a method int he cfc. To get around it use onRequestStart or do a check to see if the requested filename is your remote cfc. [coldfusion]

[/coldfusion]

By: gowri

gowri — Wed, 28 Jan 2009 18:56:08 +0000

i want to select one select option then it efect will show on to the another select option box

By: Scratty

Scratty — Sun, 17 Feb 2008 18:49:33 +0000

Sid,

I agree with you on calling the CFC directly. The URL method seems more like a hack to me, but ….

On the onRequest(), Ben Forta’s reply was:

“The onRequest() issues sounds sounds like the same limitation with Web Services and more, and is documented as a restriction.”

Make sense but a bit limiting.

By: Sid Maestre

Sid Maestre — Sun, 17 Feb 2008 18:17:09 +0000

Thanks for the post on binding to a cfselect. Have you found out why the OnRequest function in the application.cfc file interferes with cfselect data binding? I was having the same problem and your solution worked for me.

I found a work around using bind=”url:ajax.cfm?action=getStuff()” as a substitute for bind=”cfc:cfc.foo.getStuff()”

I prefer calling the cfc directly for security reasons.