with nh validator we can define a property eg as not nullable. despite
this definition we can call the setter of that property with a null
value argument. but if we then call IsValid, we know that the
operation was invalid.

if that property triggers some other events in our domain, eg raises a
property changed event and that event causes a subscriber to send
notification emails, we'll get into troubles. this is just one example
but the problem is, that we can execute operations which invalidate
our domain entities and afterwards we check if that operation was
valid.

what is the recommended usage of nh validator to avoid these problems?

--

You received this message because you are subscribed to the Google Groups 
"NHibernate Contrib - Development Group" 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/nhcdevs?hl=en.


Reply via email to