Do to the recent changes we made with CacheListener behavior I need to refactor the POJO notification implementation. In order for me to deliver reliable detach and collection remove notifications, I have to do some advanced state tracking. To do this I need to know two things: | * Correlate pre and post requests - Since concurrent requests can be delivered from different transactions/threads I might associate the wrong requests. So I need a tx id with every notification. | | * TX end notification - I need to track all changes of a certain type within the lifespan of a TX (since a single pojo operation is always multiple cache operations, and thus always in a transaction) | -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054724#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...