Hi all, just a short reminder that this issue has not been solved. I still apply two patches, one for SerializableType (adding the type info) and one for EntityPropertyInstance to prevent the null proxy.
regards, phil Niclas Hedhman wrote: > > You are probably right and we are not talking about the same thing. I'll > try > to peek at it when I am a computer tomorrow... > > -- Niclas > > On Aug 31, 2009 6:26 PM, "philippe van dyck" <[email protected]> wrote: > > Thanks you for this 'inner workings' overview, very instructive, but I am > not sure we are talking about the same thing. > It is about calling some VC Properties set methods *from inside* a > composite > (very probable case) and getting the VC proxy nullified when it leaves the > confines of the composite. > Then when you call UoW.apply(), you get an exception... this is not a rare > case. > So, if you mean that I have to call dereference when I set() the VC > Property, sometimes, It will be, IMHO, very hard to learn Qi4j, since it > works for entities... and not for VC! > > phil > > > Le 29 août 2009 à 04:49, Niclas Hedhman a écrit : > >> > I am not at the computer atm, but if you are talking about getting rid > of dereference(), then ... > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > > -- View this message in context: http://www.nabble.com/ProxyReferenceInvocationHandler-appears-in-Value-JSonization-tp25175955p25342793.html Sent from the Qi4j-dev mailing list archive at Nabble.com. _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
