I'm not acquainted with Web Projects and Rhino, you may try your workaround and if it works, then go to Rhino forum and ask for help on using their UnitOfWork which has some options you will want to use and may lose if you don't initialize its UnitOfWork...
I know a lot of people is working with Rhino and it might be only a fact of learning how to use it the right way... Gustavo. On Sun, Sep 7, 2008 at 8:27 PM, Gildas <[EMAIL PROTECTED]> wrote: > > Hi Gustavo, > > I'm using Rhino's UnitOfWorkApplication as a base for my > HttpApplication class. You're right, the problem may be here. > > Checking the UnitOfWorkApplication code, I just saw that the > NHibernate session is stored in the ASP.NET <http://asp.net/> Session if > Http Session is > available. > > 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 ? > > Anyway, I will override the Begin Request handler, create the NH > Session myself and see what I get. > > Thanks > > On Sep 7, 8:12 pm, "Gustavo Ringel" <[EMAIL PROTECTED]> wrote: > > Hi Gildas in the case you are describing the thing that it is broken is > the > > first level session. In fact you are saying that you close a session, > open a > > new one and you have the entitites already in the first level cache. > > > > If that was happening, every one is going to be reporting a > > catastrophe...because a new session cannot have things in the first level > > cache. > > > > If you are arriving to 1st level cache big chances are that your session > > management is the problem. > > > > I don't see where the problem with the 2nd. level cache is here, even if > it > > was broken. > > > > I can tell you from my own experience that 2nd level caches is working > fine > > for me with the trunk, but i did not take a look to Craig's test case... > > > > Gustavo. > > > > On Sun, Sep 7, 2008 at 8:07 PM, Gildas <[EMAIL PROTECTED]> wrote: > > > > > Well, I create a new NHibernate session at each requests. First level > > > cache is destroyed when the session is disposed at the end of the > > > request, right ? > > > > > So, when I am in debug mode on the NHibernate project, I should at > > > least once reach the code which loads an entity from the second level > > > cache before this entity can be available in the first level cache. > > > > > I do hope the problem is in my code but from what I can see with the > > > test case submited by Craig, I think something is broken with the > > > second level cache management in NHibernate. > > > > > On Sep 7, 7:59 pm, "Fabio Maulo" <[EMAIL PROTECTED]> wrote: > > > > 2008/9/7 Gildas <[EMAIL PROTECTED]> > > > > > > > Sure, but why is it always in the Session Cache ? > > > > > In a per request session mode, the Session cache is restarted at > each > > > > > request or do I have misunderstand this ? > > > > > > > Before I updated the NHibernate to the last trunk version, at each > new > > > > > request, the second level cache was requested before the entity can > be > > > > > available in the first level cache. > > > > > > If entities instances are in the sessionCache is not for magic... ;) > > > > > > -- > > > > 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 -~----------~----~----~----~------~----~------~--~---
