We are now going to input some code in order to illustrate the business-object pattern. However, we must again pay attention to the fact that there is likely another approach to getting the results. For instance, we could use an O-R Mapping (JPA or Hibernate technology) to map the entities.
As an example, the Professor
entity has an n-to-n relationship with the Discipline
entity, which is done with a JPA annotation. However, we know that there are many more use cases here than simply mapping entities.
We will use ProfessorBO
, Professor
, Discipline
, ProfessorDAO
, and DisciplineDAO
. Let's take advantage of the classes shown in the Session Façade example. We made a small change in the AcademicFacadeImpl
class. Now, this Session Façade uses a BO called ProfessorBO
to handle the business related to Professor
.
Let's review the ProfessorBO
class:
import java.time.LocalDate;
import java.util.List;
import javax.inject.Inject;
public class ProfessorBO {
private...