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.
Can I ditch the persistence.xml file on JBoss?
I have a Spring based app where another programmer is using JPA’s persistence.xml file to define the setup of hibernate and to define the entities that are being persisted.
Can I ditch the persistence.xml file on JBoss?
I have a Spring based app where another programmer is using JPA’s persistence.xml file to define the setup of hibernate and to define the entities that are being persisted.
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.
factory methods in JPA entity classes. anti pattern?
I started using factory methods in JPA Entity classes. But I’m not sure if it’s an anti-pattern. If it is , then where do I place them instead ?
A similar sample is below