2009/7/10 Tolomaüs <[email protected]> > > > I'm sorry but lazyLoading mean : verify what do as late as possible.We > > > can't check the cache before create a proxy, here I can say that is by > > > design and it will stay as is. > > I'm not sure if I can follow here. What harm could it do to check the > cache before creating the proxy while hydrating an entity? It already > checks the session cache so why not extend it to the second level > cache as well?
NH check the session-cache just before check the cache and that is the reason you have the exception... > Anyway, the workaround solution that you proposed (i.e. check the > cache and throw the exception only when real access to db > is needed) would be fine as well but doesn't the "proxy wrapper" need > a session in order to consult the cache? (with proxy wrapper I mean > the dynamically generated proxy subclass) If we implement that it will be not a workaround or if you want try to provide a patch. Thanks. -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
