DDD is not a technology or methodology. It is a way of thinking and a set of priorities aimed at accelerating software projects that have to deal with complicated domains (http://www.domaindrivendesign.org ).
For many years, designing and realizing JEE application has meant moving Data Transfer Objects (DTO) and Value Objects (VO) between layers and writing procedural code to allow Enterprise JavaBeans (EJB) to do their work.
This led to the use of classes that were defined as anemic by Martin Fowler (http://martinfowler.com/bliki/AnemicDomainModel.html), that's to say, classes where the business logic is completely separate from the domain objects; usually it is in a service layer, which uses the domain classes as classes of data.
The business logic is contained in services using anemic domain models. But as we have seen, the application works in a procedural way, and is not object-oriented. The objects are mere carriers of data realized as DTO or VO, with only the...