From: Mike D. <mik...@gm...> - 2004-11-11 20:39:24
|
This is the base class where most of the proxy work is handled. The method Invoke at the bottom contains the logic. http://cvs.sourceforge.net/viewcvs.py/nhibernate/nhibernate/src/NHibernate/Proxy/LazyInitializer.cs?rev=1.1.2.5&only_with_tag=alpha_avalon-proxy&view=auto Here's the class the proxy used to get serialized as and deserialized from. http://cvs.sourceforge.net/viewcvs.py/nhibernate/nhibernate/src/NHibernate/Proxy/Attic/AvalonProxyDeserializer.cs?rev=1.1.2.2&only_with_tag=alpha_avalon-proxy&view=auto Thanks for such as fast response! Mike On Thu, 11 Nov 2004 18:34:41 -0800, hammett <ha...@uo...> wrote: > Hey Mike, > > > In the new version it looks like GetObjectData is > > completely handled by the DynamicProxy and never handled by > > IInvocation - is that true or am I doing something wrong? > > Yes, you're right. > > > My old logic was to serialize the class instance that was being > > proxied if it has been read from the db, or if the class had not been > > instantiated yet then serialize a class that was capable of recreating > > the proxy during deserialization. I'm open for any suggestions on how > > to handle this with the new code base. > > Well, this is what the GetObjectData implementation in the proxy does... > But, to be sure that we are on the same page, can you please direct me to > the source code of the old logic? > > -- > Cheers, > hammett > http://www.digitalcraftsmen.com.br/~hammett > > |