>
> As the OP is developing a Windows Service app, I think it's better to use
> CallSessionContext or "call", which internally use CallContext for *
> temporary* session storage. For a web app, "web" (or
> WebSessionContext) is better used, which internally use HttpContext for 
> *temporary
> *session storage.
>

Agreed, still, my opinion is that this method to resolve an nhibernate
session would only be used in scenarios where injection is not possible.
For example, I would not use this in MVC apps.

-- 
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.

Reply via email to