The BeanBox implementation we are using currently has two limitations.
Every action triggered by an event has to be specified beforehand.
It is not possible to change the event structure dynamically and adapt to changing requirements. One solution to this problem is the extension of the event model with conditional events. One solution could be to specify the condition that has to be met as part of the event's adapter classes. This problem can be solved like the previous one by simply extending an event's adapters. The adapter would translate the event and thus would allow to call methods with other arguments too.