The current implementation of EventListeners looks like I can have only one of each type, i.e. only one postUpdateEventListener. I would like to have a list or set of postUpdateEventListeners. The reason is that we have the need to insert a history record based on data changed on multiple tables.

Currently, I have a budget and budget history table. When the budget is updated, I need a budget history record created that stores the old state of the budget. I implemented a budgetPostUpdateEventListener that creates the record when an enitity type of budget is updated.

Now I would like a userPostUpdateEventListener. Should I put in a JIRA request to extend the EventListeners to be a list of listeners of each type?

I do not think it is desireable to have a big switch statement inside of my postUpdateEventListener.

I believe you could use chained interceptors.

Read: http://www.hibernate.org/92.html

Yes, I had thought of that. That model does make sense for the interceptor.

However, for the event model, I would have to re-implement the chaining for each event I need to chain. It would be far better if that support was already in hibernate. For example, if I needed to do something with the FlushEntityEvent I could just add an additional listener as opposed to extending or implementing the functionality of the default FlushEntityEvent.