title: Concrete examples on why the 'Anemic Domain Model' is considered an anti-pattern
body: <p>I apologize if this is a duplicate, but I couldn't find any concrete examples on the topic in related questions.</p>
  
  <p>After reading <a href="http://martinfowler.com/bliki/AnemicDomainModel.html">Martin Fowler's article on the 'Anemic Domain Model'</a>, I'm left wandering as to why is this considered an anti-pattern. Even does the majority of enterprise developers consider it an anti-pattern, since AFAIK probably 90% of the j2ee applications are designed in an 'anemic' way ?</p>
  
  <p>Can someone recommend further reading on the topic (other than the 'Domain Driven Design' book), or even better, give a concrete examples on how this anti-pattern is affecting application design in a bad way.</p>
  
  <p>Thanks,</p>