AjaxCFC for jQuery Alpha3 Release

What can I say. I may be a pain but only because I'm one of the biggest fans of your work. :o)

Its good to have someone to push you every so often. ;o)

Thank you!! I love ajaxCFC so thank you very much for all of your great work!

John, give us a test link to see whats happening.

By the way, cfjson returns a very large amount of whitespace when deserializing. If you could add output="no" to the cfcomponent and cffunction tags in the version included with ajaxcfc it would be most helpful.

I'm a bit confused as to what is being used, and for what exactly: jquery, dwr, and your cfc?

if so, why do we need dwr and jquery? Why not just jquery alone with your cfc? And how much does all that clientside js weigh?

Or is the dwr stuff all serverside?

Thanks.

Rob/All,

Periodically, and only in firefox, ajaxCFC calls will fail to get any response from the server. This can be immediately fixed by clearing all private data (cache, cookies, etc), and then it works perfectly.

Any idea why this is happening, and is there a way to prevent it on the server side?

Since I'm obviously the second one to get tripped up on this I figured I'd post how I resolved it to make it easier on the next person. If you are using prototype sytnax you'll have to change it to jquery sytax. For example:

$('completedtab').style.display = "none"; //prototype
$('completedtab').innerHTML = r; // prototype
must be changed to this:
$('#completedtab').css("display","none"); //jquery
$('#completedtab').text(r); //jquery

I assumed incorrectly that the error was buried deep in the AjaxCFC Jquery framework; it's not. Any javascript error will be displayed in a popup window.

Since we are standardizing on jquery this is an important release for us. Thanks to all involved.

I can't seem to get debugging turned off (at least the helper window keeps pooping up)...

Out of all this, what can I remove for production?

<script type="text/javascript">
   // additional files
   $.AjaxCFC({require:'json'});
   // more additional files
   //
$.AjaxCFC({require:'json,wddx,dDumper,log4j,DWRSyntax,blockUI'});
   // optional global settings
   // using these setters also automatically include dependencies
   $.AjaxCFCHelper.setDebug(false);
   $.AjaxCFCHelper.setBlockUI(false);
   $.AjaxCFCHelper.setUseDefaultErrorHandler(false);
   $.AjaxCFCHelper.setSerialization('json'); // json, wddx
   $.taconite.debug = false;
   $.taconite.enableAutoDetection(false);
</script>

btw - I'm loving this whole Ajax process thanks to you... smooth, clean, simple, THANKS!

- Thomas

Help, I get an "unterminated string constant" error in IE6 when using wddx serialization. I tried grabbing the latest Alpha but it's still not working. Seems to work ok in Firefox, although one of my coworkers is having problems with a fatal error on Firefox as well - they may be on an older version of Firefox. Any help is appreciated.

Josh, CF encodes quicker using wddx than json, however, a wddx string is longer and it takes longer to decode in the JS side. CF8 will include native json encoding, thus it will improve CF's performance there. Overall, I tend to use json more than wddx.
HTH

I was having a heck of a time getting this to work with json input and getting back a struct in a simple echo-esque demo.

It turns out that there was a problem in json.cfc. The version in the AjaxCFC jquery branch in the riaforge repo is 1.6b, I replaced that with 1.7 from http://www.epiphantastic.com/cfjson/

That seems to have fixed it. Hope this helps someone else.

Jeffrey

This is a great tool...if I can get it working. I'm trying to integrate the newest alpha release into a Mach-II installation to no avail. Has anyone had success with it?

I know that there is a contactManager sample app of a previous version that was Mach-II integrated but these alphas seem to have some significant differences from that old version. Thanks in advance.

Gene, could you send me the updated code so I include it with the distribution?

Thanks