Composition Vs Aggregation in Java

Extending your code

 

Extensibility of a class doesn't always depend on inheritance. Using composition and aggregation relationships between classes, we can create more cohesive and loosely coupled modules. Did I say no inheritance?

 

 

Let's first understand composition and aggregation in the real world. Let's say you are a student pursuing studies in a college in the Computer Science department. If you are wearing the Object-Oriented Analysis and Design (OOAD) shoes you could easily understand the entities from the scenario. You guessed it! Student, College and Department.

 

A college has many departments and many students. The departments of the college can't exist without the college itself . This means “Departments” are owned by the college. Students can exist without the college, the ownership of students are not in the college alone. Students can look for a new college if the college doesn't exist. Can you identify a composition and aggregation relationship?

 

Composition is the idea of an object could be made up of, or composed of, other objects. The composed objects are intrinsic to the main object. Aggregation states that an object can bring together separate objects that has their own lifetime. The relation between body and heart is composition whereas car and wheel is aggregation.

 

 

Let's look at a more practical example in Java. An employee has an address and insurance. The insurance is optional for the employee but the employee should always have an address.

 

 

The lifetime of the address instance is intrinsic to the employee instance, but an insurance instance can exist on its own. If you see the code below in the Test class, once the employee instance is created, the address instance is also created within the employee class. The insurance instance is set explicitly and it is optional for an employee.

public class Test {

    public static void main(String[] args) {

        Employee kannan = new Employee("kannan sudhakaran", "Andheri", "mumbai", "Maharashtra", "5055");
        System.out.println(kannan);


        //add via aggregation
        InsuranceInfo insuranceInfo = new InsuranceInfo();
        insuranceInfo.setPolicyId("1001");
        insuranceInfo.setPolicyName("Life Insurance policy");

        kannan.setInsurance(insuranceInfo);

        System.out.println(kannan);
    }

}

 

A quick sketch of the class diagram should look like this.

 

 

The following is the implementation in Java.

// Employee.Java
package com.techlabs.composition.aggregation;
public class Employee {
    private String name;
    private AddressInfo address;
    private InsuranceInfo insurance; // may or may not


    public Employee(String name, String street, String city, String state, String postalCode) {
        this.name = name;
        this.address = new AddressInfo();

        address.setCity(city);
        address.setState(state);
        address.setPostalCode(postalCode);
        address.setStreet(street);



    }
    public String getName() {
        return name;
    }
    public void setName(String name) {
        this.name = name;
    }
    public AddressInfo getAddress() {
        return address;
    }
    public void setAddress(AddressInfo address) {
        this.address = address;
    }
    public InsuranceInfo getInsurance() {
        return insurance;
    }
    public void setInsurance(InsuranceInfo insurance) {
        this.insurance = insurance;
    }

    @Override
    public String toString() {

        StringBuilder retValue = new StringBuilder();
        retValue.append(name).append(" ")
            .append(address.getStreet()).append(" ")
            .append(address.getCity()).append(" ")
            .append(address.getState()).append(" ");

        if (insurance != null) retValue.append(insurance.getPolicyId()).append(" ")
            .append(insurance.getPolicyName());

        return retValue.toString();


    }

}
// AddressInfo.Java
package com.techlabs.composition.aggregation;
public class AddressInfo {
    private String street;
    private String city;
    private String state;
    private String postalCode;

    public String getStreet() {
        return street;
    }
    public void setStreet(String street) {
        this.street = street;
    }
    public String getCity() {
        return city;
    }
    public void setCity(String city) {
        this.city = city;
    }
    public String getState() {
        return state;
    }
    public void setState(String state) {
        this.state = state;
    }
    public String getPostalCode() {
        return postalCode;
    }
    public void setPostalCode(String postalCode) {
        this.postalCode = postalCode;
    }
}
//InsuranceInfo.Java
package com.techlabs.composition.aggregation;
public class InsuranceInfo {
    private String policyName;
    private String policyId;

    public String getPolicyName() {
        return policyName;
    }
    public void setPolicyName(String policyName) {
        this.policyName = policyName;
    }
    public String getPolicyId() {
        return policyId;
    }
    public void setPolicyId(String policyId) {
        this.policyId = policyId;
    }
}