Quoting Rickard Öberg <[email protected]>: > On 2010-11-26 18.25, Paul Merlin wrote: > > I would like Qi4j to provide such facility, in other words, allowing Qi4j > > instanciated _Objects_ to be (de)serialized and their injections to be > > reinjected after deserialization using the java transient mechanism. > > > > Can someone enlight me about what work would be needed to make the Qi4j > > runtime able to fullfill this need? > > If I remember correctly from last time I looked at it one of the issues > is that you need to provide your own ObjectInputStream, in order to get > classloading and contextual stuff (like DI) to work. You may also want > to do state replacement (i.e. serialize a Value to JSON, and then back). > For values and transients this might work ok. Services are by definition > un-serializable, and entities are tricky (but still possible with a > replacement strategy). > > So the main question is really whether you can provide your own streams > or not?
Given qi4j enabled Objects serialization is working, having concerns on the readObject methods could do it ... despite the fact that the readObject method is private. WDYT? All this is pretty foggy to me for now, need to take time I think. /Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
