coldboxproxy extension doesn't recognize access method of super

I'm using coldboxproxy.cfc to make a CFC call from a cfgrid to
populate it with data. It works fine if I place the functions in the
local app's coldboxproxy.cfc (my calendar app is a sub-ap of the main
website), but I figured I'd want to do this with many apps across the
site, so I'm trying to place them in a root proxy.cfc and then call a
proxy that extends this root cfc. this is where i'm running into
trouble. I'm using "calendar.coldboxrootproxy.cfc" to extend
"handlers.coldboxglobalproxy.cfc". When I try to generate a cfgrid via
<cfset args.bind =
"cfc:calendar.coldboxrootproxy.getCFGridData('admin.calendars.dspCalendarsRemote',
{cfgridpage},{cfgridpagesize},{cfgridsortcolumn},
{cfgridsortdirection})">
I get the following error message:
Error Messages: The specified function getCFGridData on the CFC
calendar.coldboxrootproxy must have its access attribute set to
'remote'.

So it sees the function, but doesn't see it's access method properly.
Am I missing some basic CF principle here? Or is there a Coldbox
setting I should check? Just wondering if anyone has any ideas to
point me in the direction of where I should look for my error?

Thanks!

-webroot
  -calendar
    -coldboxrootproxy.cfc
  -handlers
    -coldboxglobalproxy.cfc

calendar.coldboxrootproxy.cfc:

Hi,

I think its bug in CF but it does work when we deal with web-services.

I would suggest to use handlers.coldboxglobalproxy.cfc in <cfset
args.bind = "handlers.coldboxglobalproxy.cfc">

=== Just for Info ===
/your-url/calendar/coldboxrootproxy.cfc?wsdl you would be able to see
all methods.

make sure if webservices name exists then refresh cf-admin interface
(Web Services).
===== ====

Thanks
Sana

Use FireBug extension of FireFox to see your remote call.

Thanks for the tip on checking it via webservices. Calling it as a
webservice, it works just fine as had expected it to, so maybe there
really is a bug in the way cfgrid calls the CFC? I tried changing the
code as Sana suggested by calling the
"handlers.coldboxglobalproxy.cfc" directly and it at least returns the
page but with no data. Now using Firebug I can see the error being
returned is "Error including config file: Could not find the included
template /handlers/config/routes.cfm." so I'm guessing that's I have a
mapping issue somewhere in my app.

Thanks for the tip on checking it via webservices. Calling it as a
webservice, it works just fine as had expected it to, so maybe there
really is a bug in the way cfgrid calls the CFC? I tried changing the
code as Sana suggested by calling the
"handlers.coldboxglobalproxy.cfc" directly and it at least returns the
page but with no data. Now using Firebug I can see the error being
returned is "Error including config file: Could not find the included
template /handlers/config/routes.cfm." so I'm guessing that's I have a
mapping issue somewhere in my app.

Hi

Check ColdBox sample applications, there is CF8Ajax sample for
(CFGrid, CFWindow, CFTab etc.)

coldfusion8 ajax stuff actually introspect the cfc and on runtime
loads all methods.

So actually when you extend the cfc then it does not work, thats why I
said its CF8 bug.

Hopefully this will be fixed in coming hotfixes.

Thanks
Sana