In trying to implement MagmaPersistency it turns out
that the fact
that
PRContext holds a local cache to the current session may be a bit
of a
pain. Not only may there be a lot more stuff accidentally persisted
through this reference, there may actually be objects that magma
gurus
say 'don't persist these if you know what is good for you'.
What kind of cache?
PRContext>>session
"Answer the cached seaside session, this is a short-cut to
avoid to
unnecessary lookups."
^ self propertyAt: #session ifAbsentPut: [ WACurrentSession
value ]
This kind of cache!
I see, this is not really useful if you use a persistency mechanism
that dumps out the whole objects. The idea was that Pier knows using
the description what parts of the objects to serialize, something
that is probably not easily controllable with a framework using the
Smalltalk reach-ability to serialize objects.
So I would suggest that you remove this cache.
What's the trouble with MAProxyObject instances?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch