Thanks Fabio, I'm currently doing something like this:
public decimal Total
{
get { return calculateTotal(); }
set { } // I really don't like this
}
Supose that calculateTotal() depends on several other properties and that its result changes because of several other things besides the AddItem method... I'd prefer to calculate it every time rather than clutter the other properties setters with InvalidateTotal calls.
What do you thing about adding a "read-only" access strategy to NHibernate? I could try to do it if it is posible.