>> While I am aware that we could sprinkle our locks around .. should we have to? Can we avoid these types of hard to find copy/paste bugs by allowing say a declaration that an object is an aggregate root? <<
Take into account though that your logical region of validation differs based on what you are doing. As you said earlier you might have an OrderLine as an agg-part of two completely unrelated agg-roots, in this case there is no logical way to identify the agg-root from the OrderLine unless you have some context as to what action is being performed. Tracing back from OrderLine cannot possibly give you the right parent entity in this scenario. >> I don't have any notion of fetching strategies because if possible I avoid RDBMS. << NH will allow you to specify fetching strategies without any DB specific coding at all. If you are able to specify why you want something in addition to what it is you want then you can use a plan to fetch all the data as efficiently as possible and as you know the intention behind the fetch you will also be able to place the correct locks in the fetch. In your previous DDD apps how do you identify the correct agg-root to update? Pete --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to nhusers@googlegroups.com To unsubscribe from this group, send email to nhusers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
