Is it ok for entities to access repositories?

by

it’s not a horrible violation of DDD it’s a horrible violation of… well… it’s just plain horrible (i say this tongue in cheek) :).

First off, your entity becomes dependent on having a repository… that’s not ideal.
Ideally you’d want to have your repository create the Person and then assign it everything it needs to be effective in the current domain context.

So when you need a Person, you’ll go personRepository.GetPersonWithDefaultEmployer() and get back a person which has default employer populated. The personRepository will have a dependency on an employerRepository and use that to populate the person before returning it.

PersonReposotory : IPersonRepository
{
    private readonly IEmployerRepository employerRepository;

    //use constructor injection to populate the EmployerRepository
    public PersonRepository(IEmployerRepository employerRepository)
    {
        this.employerRepository = employerRepository;
    }

    public person GetPersonWithDefaultEmployer(int personId)
    {
        Person person = GetPerson(personId);
        person.Employer = employerRepository.GetDefaultEmployer(personId);
        return person;
    }
}

More Related Contents:

  1. What’s an Aggregate Root?
  2. How are Spring Data repositories actually implemented?
  3. What is the difference between DAO and Repository patterns?
  4. What are the benefits of Persistence Ignorance?
  5. Where do I find some good examples for DDD? [closed]
  6. Value vs Entity objects (Domain Driven Design)
  7. DDD – the rule that Entities can’t access Repositories directly
  8. How are Value Objects stored in the database?
  9. Communicating between two Bounded Contexts in DDD
  10. Aggregate Root references other aggregate roots
  11. EF codefirst : Should I initialize navigation properties?
  12. Generic Repository With EF 4.1 what is the point
  13. How to implement Unit Of Work pattern with Dapper?
  14. Entity Framework 4 CTP 4 / CTP 5 Generic Repository Pattern and Unit Testable
  15. Making Entity Class Closed for Changes
  16. EF Including Other Entities (Generic Repository pattern)
  17. Should services always return DTOs, or can they also return domain models?
  18. How to implement Generic Repository Design Pattern with Dapper?
  19. An object with the same key already exists in the ObjectStateManager. The ObjectStateManager cannot track multiple objects with the same key
  20. When to use PerThreadLifetimeManager?
  21. Should I abstract the validation framework from Domain layer?
  22. Generate POCO classes in different project to the project with Entity Framework model
  23. Looking for a Ninject scope that behaves like InRequestScope
  24. MVVM: Binding to Model while keeping Model in sync with a server version
  25. Get all associate/composite objects inside an object (in Abstract way)
  26. Proper Repository Pattern Design in PHP?
  27. Using Simple Injector with Unit Of Work & Repository Pattern in Windows Form
  28. DDD Approach to Access External Information
  29. DDD, Anti Corruption layer, how-to?
  30. Where to convert business model to view model?

Leave a Comment