On Mon, May 17, 2010 at 9:46 PM, Marcel Reutegger <[email protected]> wrote: > I just stumbled over the method > AbstractBundlePersistenceManager.load(PropertyId), which I think might > be related to this issue. > > what if the items states in the SISM indeed get cleared because the > local item states go into the change log? I guess this is more likely > the bigger the change set is, right? > > usually, this is not a problem because the item states are reconnected > with possibly new ones loaded from the persistence manager. now the > problem with above mentioned method could be the way it loads the > jcr:mixinTypes property. the property is not stored as a regular > property. the names are serialized with the node and the property is > created on the fly and always with modCount 0 (I think). > > opinions? > > I think there is also another issue with that method. the > jcr:mixinTypes property always seems to exist from the persistence > manager POV. IIUC, it will create a property with an empty value array > even if there is no mixin types set.
I actually was able to create a unit test that recreates the problem AND found the root cause. I will share this on the list a bit later today. It is a combination of factors, but a true problem. \Berry
