Niclas Hedhman wrote: > Gang, > > I find this blog (and comments) entry quite interesting, for several reasons; > > http://debasishg.blogspot.com/2007/07/domain-driven-design-handling-alternate_3757.html > > First of all, the recognition that "Business Rule Violation" is a > strong domain concept, that my GutFeeling(tm) says we should support > directly. > > Secondly, is it only me, or is the "if/else" vs "try/catch" debate > completely meaningless, as they are both totally wrong? Shouldn't the > doUpdate() return some form of action item, which always has to be > acted upon, even in the non-violation case?
I would agree, especially considering my previously mentioned thoughts on the GIT presentation, and how we could view Aggregates and updates to those Aggregates sort of like merges, and Business Rule Violations would then be similar to "merge failures", which should be embraced as not an exception but instead treated as normal. Having a way to deal with these violations in an orderly fashion would be great I think. I have no idea how to do it right now though :-) /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
