It turns out it is commitProperties of the ADG that calls super.dataProvider which means ListBase registers that handler and then the next line ADG itself registers the overridden handler with a different priority so you get two listners with same handler one with priotity 0 and the other priority default handler.
--- In [email protected], Alex Harui <[EMAIL PROTECTED]> wrote: > > It would be unlikely for the same event instance to hit the same handler in an instance twice, unless someone has registered both a method and an override of that method, had registered at different priority levels, one uses capture phase and one does not, or different instances with the same event properties each got fired. > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of reflexactions > Sent: Thursday, September 04, 2008 9:36 AM > To: [email protected] > Subject: [flexcoders] ADG CollectionHandler called twice > > > Small issue but wondered if anyone had a bright idea. > > I have a hierarchical collection which is the source foran ADG and it > is dispatching an update CollectionEvent and it is calling the ADG > twice. > > I dumped the stack on each call and they are identical, I stepped > through the code in the debugger and basically when it dispatches it > calls the ADG, then the two cursors and then the ADG again. > > any thought on what could be causing that. > > tks >
