This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Religious Question: Does Spring favor Anemic Domain Model?

The term "domain model" describes the nouns, or data, in a system that is important to the problem you're trying to solve. The service tier – where business logic lives – manipulates the application data and must ultimately persist it (typically, in a database).

Nouns and Verbs:
The service tier describes the verbs (actions) in a system. The domain model describes the nouns (data).

I'm new to Spring and was hoping it would allow for rich POJO based domain objects carrying out the business logic (of course falling back on a thin service layer when needed, I'm not an OO Nazi ) and relying on the container for services best taken care of elsewhere (tx, security, etc).

My question is not about the merits (or demerits) of DDD, rather what is the paradigm (DDD or service/anemic based) an experienced Spring designer follows? (and why).

I'll really appreciate the responses, this is not just a philosophical question, my team is at the verge of a new project and nobody wants to use EJB, we thought Spring inherently supports the "right" kind of OO.

If I'm guilty of not searching the forums for this type of question, I'm truly sorry.