I wanted to ask the authors of EJB3 in Action about how EJB3 makes implementing domain-driven design easier. Until now the "best practice" was basically demandig an anemic domain model. The J2EE technology made quite complicated to follow the practices and ideas of domain-driven design. Now everybody who has read Eric Evans wonderful book will probabely agree that there is a better way and that this alternative way offers true benefits to all parties involved in enterprise software development.
I'd be interested to hear what the authors (and of course everybody else) think about the following issues: -what improvements that were introduced in EJB3 help solve previous hindrances for DDD -how would they apply these improvements to create a rich domain model in a typical non-trivial Java EE application -what (if any) experiences have they made with DDD in the Java EE field?
I'd be very glad to hear some thoughts about these issues.
Cheers, Patrick [ March 13, 2007: Message edited by: Patrick Scheuerer ]
Unlike previous incarnations, EJB 3 are regular Java objects and hence supports all Java features.
EJB3 entities support all features such as inheritance, polymorphism so you can easily implement a rich domain model. We have devoted a complete chapter (chapter 7) of the book to domain modeling with entities.