• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JPA design policy

 
Remko Strating
Ranch Hand
Posts: 893
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Currently I divide my code in the design of the domain model which are just the JPA-Entities in which I define the entities and the relationships between them and separate classes in which I use named Queries for selecting and updating the entities.

I believe this is a good division of the domain model and the actual gathering and updating of information.

Is this common practice or is it more common to combine both logic in one class and annotating the methods of selecting and updating as @Transient?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic