Hi Stuart - moving all the business logic to Command objects would probably be a bad idea, I agree with you on that.
How do you see/solve the "testability problem" that I was talking about? Thomas On 29 Aug., 20:09, Stuart <[email protected]> wrote: > On Aug 29, 11:40 am, Raul Carlomagno <[email protected]> wrote: > > > i think you should not inject daos into yout business entities, i like > > the concept about single responsability, so, if your biz entities > > define your business domain you are adding an extra responsability, to > > access repositories, so, i would define extra classes to manage > > business interactions... > > I agree that Single Responsibility Principle is a good thing, but what > you are suggesting here sounds close to an Anemic Domain Model anti- > pattern. > > Accessing a DAO isn't an additional responsibility. Retrieving data > from a database would be an additional responsibility, but that's what > the DAO is doing for you -- that's the DAO's responsibility. > > --Stuart --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
