From: Gavin_King/Cirrus%<CI...@ci...> - 2002-02-27 05:46:29
|
> I understand what you're saying, and I hate to be dense, but can you > point to where in the current code you depend on or take advantage of > this feature of collection wrappers? In particular, I can't see where > the collection wrapper itself (i.e., the composition of the > collection) is rolled back. Yeah. Not dense. You just spotted a bug. ;) What is meant to happen is that if the session gets rolled back during initialization of the collection then the existing collection elements will get overwritten on the next call to read(). (ie. from RelationalDatabaseSession.initialze() ) Unfortunately this won't work at present. We need a PersistentCollection.beforeInitialize() method to get the collection ready for initialization. Do you want to fix that or shall I? This lives in the "_very_ obscure bug" category, unlike other problems fixed recently :) |