What I am specifically suggesting (after only a small amount of thought, and no analysis) is that we’d change the event module to support two different things:
- synchronous event handling, where you get a callback directly from the hibernate interceptor. (This would guarantee you get the event delivered, and also allow you to rollback a DB transaction.)
- asynchronous event handling, where you get a callback “later”. (This is the current behavior, there’s a small chance that events get lost, you’re not allowed to rollback the transaction.)
- I would in fact like to make this optional, so that we can drop ActiveMQ as a requirement for distributions that don’t require async events.
@wyclif, do you know of any use cases where the event module is actually used?