I am reading this thread with interest as we also want to use
Reactor with Flex Data Services.
We haven't begun experimenting yet (but will soon), so the
comments that follow are not based on anything other than a cursory look
through the docs and wishful thinking.
1. It seems you can use FDS to manage complex object relationships
(2 methods are mentioned in the docs)
and thus use Reactor to return 'simple' objects which FDS
(via separate destinations) and the Flex client manage. This approach probably
under utilizes Reactor for managing the relationships but nonetheless seems to
be workable.
2. It would be VERY nice if Reactor could insert <cfproperty
/> tags in the right place automatically - wherever the right place is
(TO or Record). Having these tags would help anyone using Flex 2 with
Actionscript 2 to CFC object mapping; and (correct me if I am wrong) would not
harm anyone using Reactor for anything else as they would just be
redundant.
Regards
Ian
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simeon Bateman
Sent: 25 March 2006 14:12
To: [email protected]
Subject: Re: [Reactor For CF] Reactor and Flex Data Services
I had thought about putting them in the record as well. However i ran into a couple problems with that. Well i assumed I woudl have problems so I didnt go any further.
The problem that I ran into is that I use reactor with complex objects. so many of the objects I return have other objects in side them. Because of the naming scheme in reactor this is not convienent because (in theory) I would need a property called subElementIterator or subElementRecord in order to get my array of sub items to translate well.
Have you tried putting the cfproperty in the record object? Did you run into any of the problems I express above? I feel like the transfer object represents exactly what I really want in terms of an object. Plus returning the transfer object allows me an opportunity to massage some of the data so that it fits my Flex project better.
Just curious how this was working out for you. Talk to you soon.
simeon
On 3/25/06, João
Fernandes <
[EMAIL PROTECTED]> wrote:
proceeded like you did and I already reported that it works like a charm.
What Sean also mention was if we could put them in the record object instead of the TOs since AS3 can also recognize getters and setters.
-- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
