its a mistake? On Tue, Feb 9, 2010 at 11:45 PM, Fabio Maulo <[email protected]> wrote:
> what you mean with "disconnected" ? > have you called explicitly session.Disconnect() ? > > > 2010/2/9 nadav s <[email protected]> > >> i have a proxy, and a disconnected session. >> when i try to access that proxy while the session is disconnected, i >> expect it to connect the session, fetch the object and then disconnect the >> session >> instead it throws an exception about my session being disconnected. >> may be i can tell it somehow to automatically reconnect the session when >> lazy loading is neccessary, but i don't see how. when i've looked at the >> code i've seen a simple if, in both the abstract lazy initializer class, and >> in the abstract persisted collection class, that checks if the session is >> connected, and if its not, it throws the exception. >> >> i've added a config key that determines weather the session should be >> automatically reconnected by the proxy to fetch the item. if that key exists >> and it is true, the proxy will reconnect the session, fetch the object and >> then disconnect it... if its false or doesn't exist, it behaves in the >> normal way - throws an exception about not being able to fetch the >> object\collection because the owning session is disconnected >> >> On Tue, Feb 9, 2010 at 3:33 PM, Fabio Maulo <[email protected]> wrote: >> >>> 2010/2/9 nadav s <[email protected]> >>> >>> if the session if disconnected the abstract proxy initializer \ abstract >>>> persisted collection throw an exception >>>> what i've done is enabled it to reconnect just for the lazy fetch, and >>>> then disconnect >>>> >>> >>> That is the default behaviour when you have a opened collection. >>> I still does not understand what you have done. >>> >>> -- >>> Fabio Maulo >>> >>> >> > > > -- > Fabio Maulo > >
