I am observing that addition of a child to a previously empty collection results in proper inserts into DB but neither:
- invalidates collection node in JBC3
- nor puts new child entity into cache and updates collection node

Subsequent read requests hit (stale) cache and never get at inserted child. Please see this link for a post containing details of this problem:
http://www.jboss.org/index.html?module= ... c&t=151524

Is it client's responsibility to explicitly evict (empty) collections from 2nd level cache?