Logic based on modified fields of a Hibernate entity
I have a Hibernate entity object MyObject with several attributes and a service MyObjectService containing business logic dealing with MyObject. I also have a view model dealing with user input/output which uses MyOjectService. This service contains method updateMyObject(MyObject o) which is called by the view model when user changes some attributes, and it saves these changes into the database.
Dealing with Users and User-Owned Data in an API
I have a question about the way I am architecting an API.
Programmatically extending Hibernate table/entity definitions in Spring, how?
I would like to know if there is a way —maybe with AOP— to extend table/entity definitions so that I can add functionality across the board that requires persistence.
Is this database design good? What JPA Entities should I create for this design?
I am trying my hands on JPA. For this I am thinking of using the example of a student admission process as shown in the diagram below.
Is this database design good? What JPA Entities should I create for this design?
I am trying my hands on JPA. For this I am thinking of using the example of a student admission process as shown in the diagram below.
Limiting complexity in JPA programs Java/Hibernate
I’ve been working on a new application for some months now. It’s my first big JPA program, and is still in the early stages. However, the complexity of my JPA object tree is becoming a growing problem.
Limiting complexity in JPA programs Java/Hibernate
I’ve been working on a new application for some months now. It’s my first big JPA program, and is still in the early stages. However, the complexity of my JPA object tree is becoming a growing problem.
Limiting complexity in JPA programs Java/Hibernate
I’ve been working on a new application for some months now. It’s my first big JPA program, and is still in the early stages. However, the complexity of my JPA object tree is becoming a growing problem.
Limiting complexity in JPA programs Java/Hibernate
I’ve been working on a new application for some months now. It’s my first big JPA program, and is still in the early stages. However, the complexity of my JPA object tree is becoming a growing problem.
What’s the correct approach to DAO layer in presence of ORM framework
I’m using JPA/Hibernate but probably it doesn’t limit question.