I assume in 40h it will be possible to implement this feature with unit test and documentation.

%bmalkow - correct my estimate if I'm wrong

Done.

%andrzej.wojcik would you like to update events to new version event "shutdown"?

I updated implementation of Shutdown event and added test cases with inheritance, method visibility and serialization which I think are important to pass before we can mark this task as done.

Fixed. All tests passes.

Few inputs from me about new implementation:

1. Almost all looks OK and works as expected

2. I'm not sure that EventBusException should extend @RuntimeException@. Could you explain this choice?

3. In EventBusImplementation we have addHandler method and removeListenerHandler@. I think it would be good to look into naming of methods and clean up - ie. rename @removeListenerHandler into removeHandler to match addHandler method.

4. In EventBusImplementation in getListenersForEvent method, I see 2 loops - one creates list of classes and second retrieves listener - as I expect this may be called very ofter I changed this into single loop.

5. Now we have a lot of classes in main package tigase.events@, maybe it would be good to separate them, ie. into @impl@, @reflection@, @annotations

6. Missing headers in newly added java files - added some, but worth checking.

7. It would be good to allow to use other serializer for events - ie. to be able to add and use some custom serializer

Implemented.

Implementatin works ok.

%bmalkow - I made few changes to EventBus while I was working on and testing #1601

I changed default executor of event handlers and increased number of threads to (by default) use 4 * no of CPU - same as XMPPProcessors as in my opinion this feature required more threads and to algorithm to scale when there is more CPUs available.

I also implemented support for serialization of collections in events (time logged in #1601 as it was required there).