Hi again... I've tracked this down to the SlotKey property on Castle.Facilities.NHibernateIntegration.Internal.AbstractDictStackSessionStore returning a different value within the same request scope.
I step through from OnBeginRequest(object sender, EventArgs e) in the SessionWebModule and see slotKey initialised, and the stack of SessionDelegates stored against this key. Then when open session is called again in my service layer, dao layer, (or I think by the atm module) slotKey showns up as null and so is initialised again, hence resulting in the creation of a second nhibernate session. Subsquent calls return the same slotKey value and so access the same session. How can this happen? Its like the SessionWebModule gets a different ISessionManager to the rest of the application or something like that? Jordan. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
