About event processing, according to the documentation : “By default, event listeners process events in the thread that dispatches them”.
So i thought that when you use synchronous cluster, all the listener are called sequentially and in the same order. But i have noticed, that it’s not true, especially i don’t understand why listeners are not called sequentially : in other words, the methods in the listener don’t expect the end of the previous method to start (in fact, if i understand, the synchonous cluster can use other threads to call listener methods, and not only the current thread as i thought).
I like Asynchronous listener especially with
SequentialPerAggregatePolicy : is it possible to have the same behavior with a synchronous listener ? My purpose is that the thread that executes the command will have to wait until all event handling has finished (so, the user can validate a form in the user interface, and can view the result with good data, not obsolete).