exactly the problem you describe. The unsatisfactory solution has
been to put all my cfCFCsin the same directory and only call them from
that directory. Otherwise the path gets screwed up since the
braindead macromedia service can't establish different roots for CFC
in different Applications.
I spent quite a bit of time with my hosting provider to find a
workaround, but short of all applucations on the server stuffing their
CFC under the same root directory we couldn't figure it out. I would
love to hear if others have had different luck.
Craig Earls
On Mon, 05 Jan 2004 20:14:35 -0400, you wrote:
>>Has anyone used flash remoting on a shared hosting environment, as Iım
>>convinced its a problem with the path to the cfc...
>
>What hosting provider? Does it work in your local development scenario? (you do have a development server right?)
>
>Heres a snippet that should work for you:
>
>/*
>AS code
>*/
>
>obj = function () {
> this. (r) {
> trace("received:" + r);
> }
> this. (e) {
> trace("error:" + e.details);
> }
>}
>
>function init () {
> NetServices.setDefaultGatewayUrl("http://www.lightwillrise.com:27000/flashservices/gateway");
> var conn = NetServices.createGatewayConnection();
> var service = conn.getService("cfc.sendmail",new obj());
> service.sayHello();
>}
>
>init();
>
>/*
>in cfc/sendmail.cfc
>*/
>
><cfcomponent>
> <cffunction
> name="sayHello"
> access="remote"
> output="false"
> returntype="string">
> <cfset var message = "hello">
> <cfreturn message>
> </cffunction>
></cfcomponent>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
