Decorator design pattern is used to modify the functionality of an object at runtime. At the same time other instances of the same class will not be affected by this, so individual object gets the modified behavior. Decorator design pattern is one of the structural design pattern (such as Adapter Pattern, Bridge Pattern, Composite Pattern) and uses abstract classes or interface with composition to implement.
We use inheritance or composition to extend the behavior of an object but this is done at compile time and its applicable to all the instances of the class. We can’t add any new functionality of remove any existing behavior at runtime - this is when Decorator pattern comes into picture. Suppose we want to implement different kinds of cars - we can create interface Car to define the assemble method and then we can have a Basic car, further more we can extend it to Sports car and Luxury Car. The implementation hierarchy will look like below image. But if we want to get a car at runtime that has both the features of sports car and luxury car, then the implementation gets complex and if further more we want to specify which features should be added first, it gets even more complex. Now imagine if we have ten different kind of cars, the implementation logic using inheritance and composition will be impossible to manage. To solve this kind of programming situation, we apply decorator pattern in java. We need to have following types to implement decorator design pattern.
Component Interface - The interface or abstract class defining the methods that will be implemented. In our case Car
will be the component interface.
package com.journaldev.design.decorator;
public interface Car {
public void assemble();
}
Component Implementation - The basic implementation of the component interface. We can have BasicCar
class as our component implementation.
package com.journaldev.design.decorator;
public class BasicCar implements Car {
@Override
public void assemble() {
System.out.print("Basic Car.");
}
}
Decorator - Decorator class implements the component interface and it has a HAS-A relationship with the component interface. The component variable should be accessible to the child decorator classes, so we will make this variable protected.
package com.journaldev.design.decorator;
public class CarDecorator implements Car {
protected Car car;
public CarDecorator(Car c){
this.car=c;
}
@Override
public void assemble() {
this.car.assemble();
}
}
Concrete Decorators - Extending the base decorator functionality and modifying the component behavior accordingly. We can have concrete decorator classes as LuxuryCar
and SportsCar
.
package com.journaldev.design.decorator;
public class SportsCar extends CarDecorator {
public SportsCar(Car c) {
super(c);
}
@Override
public void assemble(){
super.assemble();
System.out.print(" Adding features of Sports Car.");
}
}
package com.journaldev.design.decorator;
public class LuxuryCar extends CarDecorator {
public LuxuryCar(Car c) {
super(c);
}
@Override
public void assemble(){
super.assemble();
System.out.print(" Adding features of Luxury Car.");
}
}
package com.journaldev.design.test;
import com.journaldev.design.decorator.BasicCar;
import com.journaldev.design.decorator.Car;
import com.journaldev.design.decorator.LuxuryCar;
import com.journaldev.design.decorator.SportsCar;
public class DecoratorPatternTest {
public static void main(String[] args) {
Car sportsCar = new SportsCar(new BasicCar());
sportsCar.assemble();
System.out.println("\n*****");
Car sportsLuxuryCar = new SportsCar(new LuxuryCar(new BasicCar()));
sportsLuxuryCar.assemble();
}
}
Notice that client program can create different kinds of Object at runtime and they can specify the order of execution too. Output of above test program is:
Basic Car. Adding features of Sports Car.
*****
Basic Car. Adding features of Luxury Car. Adding features of Sports Car.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
While we believe that this content benefits our community, we have not yet thoroughly reviewed it. If you have any suggestions for improvements, please let us know by clicking the “report an issue“ button at the bottom of the tutorial.
Thanks for the nice tutorial.
- Amit
I want to ask you a question.How did you draw a class diagram? which tool? Could you show some useful UML plugins for eclipse ? Thank you.
- john
You said: “Now image if we have ten different kind of cars, the implementation logic using inheritance and composition will be impossible to manage” But then you still created 2 classes for each type of car (LuxuryCar & SportsCar). So the this pattern didn’t solve the problem of having ten different kind of cars. Or what did I get wrong here ? Thank you.
- Muhammad Gelbana
I believe you should put “super.assemble();” instead of “car.assemble();” in concrete decorators. But still your tutorial is great! Thank you very much!
- ildar
Pankaj sir multiple design pattern using create Framework? example login Framework
- prakash
The relationship between a car and the decorator is inheritance, doesn’t sound quite right to call a CarDecorator “is a” Car.
- Bal
I think CarDecorator should be an abstract class in order for it to confirm to decorator design pattern ,
- Masoud
Hello. I used your tutorial to implement a Decorator, but found an error: sportsLuxuryCar.assemble(); won’t execute the assemble() method for every Decorator used when creating the instance. So the output of sportsLuxuryCar.assemble(); wont’ be: “Basic Car. Adding features of Luxury Car. Adding features of Sports Car.” but “Basic Car. Adding features of Sports Car.” instead. I think you should correct that in the tutorial, because the chain execution of the assemble() method is useful and should be invoked in constructors in order to work. Thank you!
- Agustín Labaronnie
How to print only Luxury Car? Thanks
- Arun Singh
How to get the features of Luxury Car separately if I need them for another car at my home. I assume the same scenario is for Dosa where you can get plain dosa, dosa with masala and dosa with chutney. So masala and chutney classes extend DosaDecorator. PlainDosa class and DosaDecorator class implements Dosa interface. Now what if i want extra chutney (means only chutney separately) ? Thanks in advance.
- Arun Singh