On Wed, Jun 24, 2009 at 4:24 PM, Sandro Martini wrote: > Hi Niclas, > i
think this is because of the Serializers approach, with all > serialization
details inside, and to ensure that none can transfer > object instances
where not wanted (for example GUI elements). Ok. Your starting point is of
course very different. > The problem could be with objects that are not
directly supported by > Serializers (some time ago i had a discussion with
the team, but my > proposal to generalize things has been rejected :(-
because some > things would be more complicated than current). In my case,
the situation is actually quite different. I depend on a very specific
framework[1] that as a "last resort" will also be able to store
Serializables. Since the UI information I want to store is meshed up with
many, many other non-Pivot stuff, I can't really handle the Pivot solution
either. But don't worry about it. We are talking about 6-10 classes, and I
can manage that with 'replicas'. [1] http://www.qi4j.org Cheers -- Niclas
Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live
here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I
relax here; http://tinyurl.com/2cgsug
