Changes between Version 5 and Version 6 of GROUP_FILE_ACCESSES_PERSISTENCE_R0

Timestamp:

11/06/09 15:39:12 (15 years ago)

Author:

mira

Comment:

--

GROUP_FILE_ACCESSES_PERSISTENCE_R0

@@ -34 +34 @@
 The revision persister`s logic should be separate for saving and loading. It should get the value of the PersistenceKey HISTORY_LEN and call the changes persister for the last x changes. It calls the ResourceModelPersister for the initial model. The order of those depends on the Mode. [[BR]] [[BR]]
 We will no longer need separate persisters for books, pages, frames, annotation sets, etc. Every Key  will have a method persist(). It will be used by the ResourceModelPersister for persistence of the value kept by this key in the model. The method will take arguments: [[BR]] [[BR]]
--       the persisted format. [[BR]] [[BR]]
--       ValueRef to the persisted value [[BR]] [[BR]]
--       Storage where the value should be persisted [[BR]] [[BR]]
--       and persistence options. [[BR]] [[BR]]
+-       the persisted format. [[BR]] 
+-       ValueRef to the persisted value [[BR]] 
+-       Storage where the value should be persisted [[BR]] 
+-       and persistence options. [[BR]] 
 The default behavior of this method should be to check if it is loading value that was not persisted. In this case it should just set the ref to null. Otherwise should be called the appropriate persister for the child of the given storage with name- the last part of the key`s id. The best way to find the appropriate persistence schema is using a utility method from the PersistenceUtil. [[BR]] [[BR]]
 This logic should be provided by the persistR3() method of the DefaultPersistableKey that inherits Key. The Simple and Templated Keys should inherit the DefaultPersistableKey. Some of the concrete keys in the model should override this method. [[BR]] [[BR]]