Domain objects represent important concepts in the target domain and so must often be persistent. The Java Persistence API (JPA) turns out to be quite flexible for mapping rich domain objects to relational tables. The more complex the logic you need to realize, the more easily object-oriented persistence can be maintained and developed.
The real issue with complex logic realized with anemic structures are type distinctions in the service layer. Massive if-statements might be necessary to differentiate among entity types. Every introduction of a new subclass, or even a change in the existing business logic, requires you to find, enhance, and test these type checks.
Admam Bien
you can take advantage of concept "Domain-driven design" which Adam Bien talked about in his article:
http://www.javaworld.com/javaworld/jw-05-2009/jw-05-domain-driven-design.html?page=2?