Hi. here is the problem.
When the client side ask for some object (Obj) that contains a many-to-one property (LazyClassProp), this property doesn't come initialized becouse it's class is lazy.
But when the remote object serializes this object (Obj), the serializer tries to initialize it, and I don't know why the serializer does.
I don't want it, I want the object (Obj) goes to the client side with that property not initialized, so, when the property whith the lazy class is accessed into the client, the remote object intercepts the initialization and request the initialized object.
I don't konw how to do this.
Last edited by anuarneto on Tue Oct 31, 2006 4:32 pm, edited 1 time in total.
|