It seems that the implementation that is targeted in the current_session_context_class property either has this behaviour or not.
In my unittest configuration I was using "thread_static" and that does not seem to implement the behaviour that I expected. Now using "NHibernate.Context.CallSessionContext" and that seems to work fine at the moment. The following article provides some more information about the implementations shipped with NHibernate itself. http://knol.google.com/k/fabio-maulo/nhibernate-chapter-2/1nr4enxv3dpeq/6#H3-2-3-Contextual-Sessions Their it also clearly mentions " This context only supports one session factory. " at the thread static implementation part. Grtz, Ramon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
