Details
Description
The event subscription infrastructure introduced in activiti 5.9 should be expressive enough to add support for catching intermediate message events.
AT:
- catching intermediate & boundary message events can be parsed correctly
- there is an API method which allows to signal to activiti that a message has been received.
- message correlation is performed "outside" of activiti
- there is a query method which allows to query for executions which have subscribed to a particular message event.
Should we do message boundary events in this issue as well or create a seperate issue for that?