Or change the
way objects are cached, see the subclasses MAMemento.
We once used OmniBase together with Magritte and there we introduced
a special subclass of MAMemento resolving proxies and validating
changes with respect to the database (conflicts, concurrent
modifications, etc). I guess something like that could help in your
context as well.
That sounds good, too. To enable it I have to change
Object>>mementoClass I guess. Is there any other way to select a
specific mement class?
Yes, there is no other easy way right now. In fact, speaking about
our OmniBase project again, we used a custom subclass of Object where
we overrode #mementoClass and where we all our model classes
inherited from.
As an attachement you find our custom memento class. Since this is
from a very old version of Magritte it won't work with current
versions (e.g. at that time the memento hierarchy was called
wrapper). Maybe you can still get some ideas from its implementation?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch