Code-lab exercise 3

JPA part I - CodeLab Exercise

This CodeLab exercise is designed to help you practice the concepts you have learned in the JPA 1 module on day 1. You will be working on a series of tasks that involve Java Persistence API, with Entities and DAOs. We will also practice pair programming and collaboration using Github.

Exercise Overview

Instructions

1. Team up (2 x 2)

1. Team up in pairs of 2
2. Find another pair to team up with
3. Create a team of 4 people in Moodle

2. Set up the development environment (one per team of 2 x 2)

1. ONE team member should clone the following GitHub repository: git clone -b code-lab-3 https://github.com/tysker/3sem-codelab-exercises.git.
2. Delete the .git folder in the project folder.
3. Create a new GitHub repository and push the project to the new repository.
4. Make everybody else collaborators on the repo.
5. Then create a new maven project with a Hibernate Config file and the appropriate pom.xml dependencies for using with JPA.
6. Create a new branch: develop and Protect the main branch and the develop branch from pushing directly to it. Only allow Pull Requests to merge into these branches.
7. Every team member should clone the new repository to their local machine
8. Checkout the develop branch (each member)

3. Connecting to the database

1. Each member should create a database in your docker environment with postgres called university.
2. Set up the HibernateConfig file to connect to the database.

4. The assignment

You are going to create a simple application for a university. The application should be able to manage students, courses and teachers. This time around we are going to add relationships between the entities. The relationships can be seen in the diagram above. Most of the code is already written for you. You need to implement the missing parts. Make sure to use the correct annotations for the relationships and try to understand how the relationships work.

Remember to write integration tests for the DAO classes.

Ask yourself the following questions before you start implementing the relationships:

• What are the relationship between the entities?
• Which one should be the owning side of the relationship and what does that mean?
• Should the relationship be unidirectional or bidirectional?
• What cascade type should be used or should we use them at all? What are the implications?
• Should we use fetch type eager or lazy and why?

5. Identify tasks, break them down and assign to pair programmers as Issues in Github

The following tasks are suggestions for the first round of tasks. You can add more tasks as you go along.

1. Create an Enum for the Course class as shown in the diagram and add the correct annotations to the Course class.
2. Implement the GenericDAO interface for the Course class.
3. Implement the GenericDAO interface for the Teacher class.
4. Implement the GenericDAO interface for the Student class.
5. Add the relations between the entities as shown in the diagram.
   • a) student can attend many courses
   • b) a course can have many students
   • c) course can have only one teacher
   • d) a teacher can teach many courses
6. Look at the dto diagram below and implement the methods in the DAO classes to get the data as shown in the diagram.

6. Start working on the tasks (round 1)

1. Create a branch off the develop branch for each task
2. Work on the tasks in pairs

7. Pull request

1. Create a Pull Request to merge the task branch into the develop branch
2. Assign the Pull Request to the other pair for review

8. Review (description of how to conduct code reviews using pull requests)

1. Review the Pull Request
2. Provide feedback
3. Merge the Pull Request and delete the branch

9. Repeat

1. Identify the next tasks
2. Repeat steps 5-8 for the next tasks