I have read Eric Evans book. I was under the impression that a Domain Model should not have dependencies injected (even repositories).
This statement is supported by questions like this: https://stackoverflow.com/questions/20035810/should-domain-objects-have-dependencies-injected-into-them, where the answerer says that "Domain Objects shouldn't depend on anything else". However, I then see this: http://www.zankavtaskin.com/2013/11/applied-domain-driven-design-ddd-part-4.html i.e. a domain service in the domain model that depends on the repository.
Should a Domain service have dependencies? I realise that application services have repositories injected.
My use case is a domain model that figures out what offers a customer is entitled to based on their preferences. There is a table in the database called offers, which contains the offer expiry date etc. Does the domain model:
1) Tell the application service that the customer is entitled to offer a, b and c. Then the application service goes to the database and gets the offers
2) The domain model (domain service?) goes to the database and gets details of the offers and returns them to the application service as a list of DTOs.