Domain driven design and transactions in Spring environment

Question

I used to design my application around anemic domain model, so I had many repository object, which were injected to the big, fat, transaction-aware service layer. This patte

Answer 1

My personal take on applying DDD with Spring and Hibernate, so far, is to have a stateless transactional service layer and access the domain objects through that. So the way I'm doing it the domain model does not know about transactions at all, that is handled entirely by the services.

There is an example application you might find helpful to take a look at. It looks like Eric Evans was involved in creating it.