Hi!

Since in winform data binding updates object values after format event (exiting from control) and when another control after that needs to load the data from the database by using session.query...

In this scenario when user wants to cancel the data manipulation then how to tell to NHibernate DO NOT UPDATE the data by loading from the database but only on session.Flush();

for this reason i avoid the databinding feature. Each of my forms implements a BindData() and UnbindData() method which do the task. It's more work but the big advantage is, that i have absolutely control over the databinding process.

You can control the save behavior of a session via the FlushMode property or via session.Evict(). You can set the FlushMode of a session to "never" which means that you are responsible to call session.Flush() by yourself. Session.Evict() gives you a chance to remove specific objects from the session cache.

Regards
Klaus

I did some research and found that n-level undo capability has developed in CSLA BusinessObject with source fully available.

now the problem is that NHibernate wants that all propertyes or funcitons are virtual, but is there some attribute that tells to NHibernate not to worry about this function or property?

in example

No, there isn't.
You can turn off proxying or build your own on a per-class level.
There are very good reasons why you need to have all properties/methods as virtual.

Can I turn of proxying on a per-class level? I did not found any material about how to do that.

Could you specify the reason why all properties/methods should be virtual, even if they does not do anything with NHibernate mapping, but extend some logic that have nothing to do with hibernate ???

But it seems that the needet time to invested on solving this is much longer than just writeing the virtual statement, so I'm probably take the eazy way...

<class lazy="false">

You need this because you might load a proxy of a type Animal, and when you resolve it you would get a type Dog.
This means that everything on the proxy has to be forwarded to the implementation. otherwise bad stuff happens, because the class invariants are broken.