What about ideas about managing NHibernate session strategy if Microsoft Composite UI Application Block and NHibernate are used together?

I'm using a Composite UI inspired architecture and after a *lot* of grief I gave in and started using long running sessions. I think after hitting the third or forth brickwall I decided that some rules ("sessions should be as short as possible") we're meant to be broken!

One reason in particular was property change events via the INotifyPropertyChanged interface. If I read the same entity out in separate sessions, they are going to be different objects that are going to fire change events independently.

Another reason was that I am proxying all classes and collections and I've yet to see a pretty solution for session on demand initialization.

Nathan

I tried to connect session lifetime to workitem lifetime but
to much troubles appeared.

What dou you think about single session?
And what do you mean by "proxying all classes and collections"?