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

Unnfortunately I haven't make myself familiar with Spring but I will give feedback about your DDD understanding. Reading your description of transaction it is obvious that you haven't understand DDD especially Aggregate, Aggregate Root, and Repository concept.

In DDD transaction can't span across aggregates so one Aggregate will always have one transaction.