Event Handler Exception Handling With Events #11

New Issue

kske · 2021-02-20T22:18:51+01:00

kske commented

2021-02-20 22:18:51 +01:00

At the moment, an exception thrown by an event handler is propagated back to the caller of EventBus#dispatch(Object) as an unchecked EventBusException.

This behavior could be improved by introducing an ExceptionEvent which is similar to DeadEvent as they both wrap other events and can only be dispatched by the event bus.

With this event, unexpected exceptions can be handled in a clean and centralized way.

Exception events must not cause dead events as this might cause an indirect recursion when a dead event handler throws an exception. Instead, system events (DeadEvent and ExceptionEvent) should not be able to produce instances of other system events.

At the moment, an exception thrown by an event handler is propagated back to the caller of `EventBus#dispatch(Object)` as an unchecked `EventBusException`. This behavior could be improved by introducing an `ExceptionEvent` which is similar to `DeadEvent` as they both wrap other events and can only be dispatched by the event bus. With this event, unexpected exceptions can be handled in a clean and centralized way. Exception events must not cause dead events as this might cause an indirect recursion when a dead event handler throws an exception. Instead, system events (`DeadEvent` and `ExceptionEvent`) should not be able to produce instances of other system events.

kske added the

enhancement

label 2021-02-20 22:18:51 +01:00

kske self-assigned this 2021-02-20 22:18:51 +01:00

kske added the

core

label 2021-02-20 22:21:27 +01:00

kske referenced a pull request that will close this issue

2021-02-21 13:54:35 +01:00

Add ExceptionEvent #12

kske closed this issue

2021-02-21 14:04:26 +01:00