Tonic, My Command does call Service (to get data from DB stored proc), and on success (in handler) has to do a little processing of its resultset to create a proper ArrayCollection. only after that I am trying to dispatch the ListLoaded event (from onSucces handler).
I have seen that working from doing dispatchToModules() directly from execute() in that app, but don't see why it works there, but not from onSuccess handler. Is there difference there? I don't think we can easily upgrade Robotlegs at that point - it's a large and complex app, and nobody else around from original developers to fix possible problems, and I am not in full control of it yet. TIA, Oleg. On Fri, Apr 29, 2016 at 4:28 AM, Tonic <[email protected]> wrote: > Hi, the command in Robotlegs normaly can't communicate with the robotlegs > eventbus. Command must execute Service (who extend Actor), and this is the > Service who dipatch Event with your result (your collection) in the > robotlegs bus event. > > In Robotleg 2.2.1, you can simply extend Command, an inject event > dispatcher > bus like this. > > > > With that, your command can dispatch to the bus without executing Service > extends Actor. > > So maybe you can upgrade your library ;) > > > > ----- > Tonic > Twitter > Folio > -- > View this message in context: > http://apache-flex-users.2333346.n4.nabble.com/Robotleg-mediator-cannot-hear-event-from-command-tp12629p12632.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. > -- Thank you, Oleg.
