Hi Seth,
when doing a FCS -- Flash Remoting call I always use the _Result/_Fault
notation in the applications main.asc file to use a callback like mechanism.
This works fine with any returned data type, i.e.
// inside the FCS script
service.myRemoteMethod(someParam, anotherParam);
] On
Behalf Of Indy Nagpal
Sent: Friday, June 10, 2005 3:55 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Flex / Flash / FlashComm, Remoting and CF
Yes...
I find that is always a good idea to have a cfm page that queries your
cfc exactly in the same manner as the remoteobject tag in your
;
Jeff
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Abdul Qabiz
Sent: Friday, June 10, 2005 8:21 AM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Flex / Flash / FlashComm, Remoting and CF
Yeah, It is always a good idea to create
firstName:String = result.firstName;
Jeff
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Abdul Qabiz
Sent: Friday, June 10, 2005 8:21 AM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Flex / Flash / FlashComm, Remoting and CF
Use all Uppers when you reference the remoting object.
I assume you're returning a struct?
If so:
return tempstruct should work fine so long as you have tempstruct.FIRSTNAME as the firstname variable name.
If you are returning a query, you'll need to referece result[0].FIRSTNAME, etc.
On
Yes...
I find that is always a good idea to have a cfm page that queries your
cfc exactly in the same manner as the remoteobject tag in your flex
app would. And use cfdump on your cfm page to examine what the cfc
returns. That way you know exactly what is being returned. And if you
are using
6 matches
Mail list logo
