Thanks Gary,
I confirmed that the CFC is accessible over a standard URL by loading
it in the Web browser.

Turing the Ajax debugging on, I can see the exact request that is
being made. I take that request, fix the URL so that it now looks in
the correct location, paste the corrected URL into the browser, and
the CFC returns a result.

-Mike Chabot

On 9/12/07, gary gilbert <[EMAIL PROTECTED]> wrote:
> Hi Mike,
>
> if you are using a virtual directory and your cfc is located somewhere else 
> you still need to be able to get to the cfc using a standard URL.
>
> I have found the the bind always starts at the webroot and goes from there so 
> in your example you have.
>
> http://mysite/projects
>
> Your bind attribute would need to be "cfc:mysite.projects.mycfc.myfunction" 
> if your cfc's are located in another virtual directory your bind attribute 
> should be.
>
> "cfc:myVirtualDir.myCFC.myfunction"
>
> A good test is to see use a standard URL to get to your CFC if you reach it 
> then you know what the path will be.
>
> example url
> http://mysite/projects/mycfc.cfc?method=myfunction&returnformat=json&argumentcollection=...
>
> Regards,
>
> Gary Gilbert
> http://www.garyrgilbert.com/blog
>
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:288276
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to