Expand my Community achievements bar.

refreshCollection vs repeated fill() calls question


Level 1

I have some flex clients that need to be notified of changes that take place outside of any Flex client LCDS applications (updates to my database takes place independent of the clients).

I'm able to listen for a CollectionChangeEvent on the managed collection that my AbstractAssembler populates, and iterate over the PropertyChangeEvents to get just the changes made since my last data refresh when I call refreshCollection() from the client, but I don't get that same change set (I end up just getting one big PropertyChangeEvent.reset event) when I simply call the same fill() method over and over from the clients with the same fill parameters.

Why is the behavior different when I use refreshCollection() versus repeated calls to the fill() method using the same fill parameters?

0 Replies