hammett wrote:
> Also, replicating dependencies on a distinct player feels like a > smell. I for one hardly have my repositories having dependencies. > But I agree that in the great scheme of things, it's the less > problematic approach.. So what is the right approach for you in my previous example? Moving out the behaviors from the entity to a service? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
