Fabio, I know that I'm still noob in NHibernate and that I may ask stupid questions. I'm sorry if you are bored with this, but well, please understand that I'm just trying to resolve a problem I did not have before upgrading to last NHibernate trunk.
Going through Rhino code, I can see that my session is created at each request, so that's not the problem. Anyway, I still don't have any second level cache. Items are updated but never retrieved from it. Can someone check the test case from craig, which is failing and don't use any fancy session management ? Thanks On Sep 7, 8:35 pm, "Fabio Maulo" <[EMAIL PROTECTED]> wrote: > 2008/9/7 Gildas <[EMAIL PROTECTED]> > > > > > So I'm going to ask if this is the right way to handle sessions ? From > > what I remember of NHibernate, NH Sessions must not be stored in > > HttpContext.Session. I may not understand the reasons why this done > > like this in UnitOfWorkApplication, maybe for long transactions > > management ? > > Rhino UoW use httpSession only for long conversation... > The NhSession CAN be stored in the httpSession simply because is the "most > simple" way to manage long-conversations. > -- > 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 -~----------~----~----~----~------~----~------~--~---
