Does Second Level Caching work on inserts?

Specifically, does Hibernate put the newly inserted record into the Second Level Cache upon successful insertion or the record or completion of transaction?

I have a situation where I am storing a object graph in one MDB, and would like to keep the data around after insertion, to be retreived by a second MDB later. I am thinking about using a distributed second level cache for this, but am not seeing the inserts happen when I test it.

Thanks in advance!

So, looking at the hibernate source, there is no mention of caching in the DefaultSaveEventListener, and only around updates in the DefaultSaveOrUpdateEventListener, and all over the place in DefaultLoadEventListener.

So, the follow up question is why isn't there caching on inserts/saves? I understand that typically you do not need the data shortly after the insert, but what if you do?

If I recall, there are some consistency reasons for Hibernate not to add elements on insertion. Distributed caching is a complex beast, and you don't want to retrieve staled data, do you ;-)

Actually it depends upon the cache concurrency strategy. Some concurrency strategies cache on insert, some don't. It's all about what consistency guarantees are made by the strategy.