this may help http://msdn.microsoft.com/en-us/magazine/ee819139.aspx

On Oct 15, 1:02 pm, Visar Uruqi <[email protected]> wrote:
> Hi
>
> I have an issue which I can not find in books or blogs
> may be it is there but I don't have the ability to see it.
> I need you to put light on it.
>
> The issue is regarding NHibernate and the session managment.
> I am involved in a desktop app project and I am using
> session per form approach So I am reading objects and writing
> in a conversation through one session ... I have sometimes problems
>
> ==================================================================
> Is it better to read objects through IStatelessSession
> and write them through UoW ISession?
>
> Click the image below to see what I 
> mean:http://www.probit-kos.com/images/example.png
>
> Is it a bad or good to do like this in a desktop application?
>
> make session, read, destroy session
> make session, re-attach objects (usually proxy's), Commit session,
> destroy
> ...
> and again open, read, close
> open, re-attach, write, close
>
> I am trying to do CpBT (Conversation per Business Transaction),
> if I leave sessions open things get messed up sometimes
> it throws trying to associate object in two sessions etc...
> This is the end of quesion 1.
>
> I have one more question just look to the example below and read the
> coment:
>
> Click the image below to see what I 
> mean:http://www.probit-kos.com/images/example2.png
>
> What do you recommend me to do?
>
> Also when I open a session I do like this:
> Click the image below to see what I 
> mean:http://www.probit-kos.com/images/screen3.png
>
> Since I don't know how to set the FlushMode to Commit
> by default I do it during session creation
>
> Visar Uruqi

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