{"id":2969,"date":"2024-01-05T16:00:13","date_gmt":"2024-01-05T16:00:13","guid":{"rendered":"https:\/\/msgprogramator.sk\/?p=2969"},"modified":"2025-07-07T10:57:22","modified_gmt":"2025-07-07T10:57:22","slug":"java-chain-of-responsibility","status":"publish","type":"post","link":"https:\/\/msgprogramator.sk\/en\/java-chain-of-responsibility\/","title":{"rendered":"Java design pattern Chain of Responsibility"},"content":{"rendered":"

Today we will look at the first Java<\/strong> design pattern<\/strong> from the category of behavioural patterns<\/strong> – Chain of Responsibility. Design patterns in this category deal with the interaction<\/strong> between objects and their responsibility<\/strong>.<\/p>\n

What is the Chain of Responsibility design pattern?<\/h2>\n

The Chain of Responsibility<\/strong> design pattern is a pattern that allows multiple objects to process requests without the object needing to know who its successor in the chain is. Each object in the chain has the ability to process the request, but if it doesn’t know how to process it, it passes it on to the next object in the chain.<\/p>\n

What problem does the Chain of Responsibility design pattern solve?<\/h2>\n

It solves the problem of processing requests in a chain, so that instead of the request being sent to a specific object, the request passes through a chain of objects, where each object in the chain can be responsible for processing the request, but if it doesn’t process it, it passes it on to the next object in the chain. The goal is to allow multiple objects to process a request without having to specify exactly which object will process it, thus reducing the dependency between the sender and receiver of the request.<\/p>\n

Example of a Chain of Responsibility implementation in Java<\/h2>\n

We will now write a program that uses the Chain of Responsibility<\/strong> design pattern to simulate the approval of employee requests in a company. The aim of this pattern is to allow multiple objects to process a request without knowing exactly which object will process it. The objects are chained together and each object in the chain decides whether it can handle the request or pass it on to the next object in the chain. <\/p>\n

There are three types of employee in this program – Employee<\/strong>, Supervisor<\/strong> and Director<\/strong>, each of which implements an abstract class, RequestApprover<\/strong>, which contains common functionality for all employees.<\/p>\n

RequestApprover.java<\/u><\/strong><\/p>\n

package designpatterns;\n\npublic abstract class SchvalovatelPoziadavky {\n    String meno;\n    SchvalovatelPoziadavky dalsiSchvalovatel;\n    private SchvalovatelPoziadavky(){\n\n    }\n    public SchvalovatelPoziadavky(String meno){\n        this.meno = meno;\n    }\n    public abstract void nastavitDalsiehoSchvalovatela(SchvalovatelPoziadavky dalsiSchvalovatel);\n\n    public void posuditPoziadavku(String poziadavka)\n    {\n        if(this.dalsiSchvalovatel != null)\n            this.dalsiSchvalovatel.posuditPoziadavku(poziadavka);\n        else\n            System.out.println(poziadavka + " - poziadavka bola zamietnuta!");\n    }\n}<\/code><\/pre>\n
The RequestApprover<\/strong> abstract class defines common methods and contains a reference to the next approver in the chain.<\/p>\n
Employee.java<\/u><\/strong><\/p>\n
package designpatterns;\n\npublic class Zamestnanec extends SchvalovatelPoziadavky {\n    public Zamestnanec() {\n        super("zamestnanec");\n    }\n    @Override\n    public void nastavitDalsiehoSchvalovatela(SchvalovatelPoziadavky dalsiSchvalovatel) {\n        this.dalsiSchvalovatel = dalsiSchvalovatel;\n    }\n    @Override\n    public void posuditPoziadavku(String poziadavka) {\n        if(poziadavka == "NAVSTEVA_LEKARA") {\n            System.out.println(poziadavka + " - " + meno + " schvalil poziadavku");\n        }\n        else {\n            super.posuditPoziadavku(poziadavka);\n        }\n    }\n}<\/code><\/pre>\n
Supervisor.java<\/u><\/strong><\/p>\n
package designpatterns;\n\npublic class Veduci extends SchvalovatelPoziadavky {\n    public Veduci() {\n        super("veduci");\n    }\n    @Override\n    public void nastavitDalsiehoSchvalovatela(SchvalovatelPoziadavky dalsiSchvalovatel) {\n        this.dalsiSchvalovatel = dalsiSchvalovatel;\n    }\n    @Override\n    public void posuditPoziadavku(String poziadavka) {\n        if(poziadavka == "DOVOLENKA") {\n            System.out.println(poziadavka + " - " + meno + " schvalil poziadavku");\n        }\n        else {\n            super.posuditPoziadavku(poziadavka);\n        }\n    }\n}<\/code><\/pre>\n
Director.java<\/u><\/strong><\/p>\n
package designpatterns;\npublic class Riaditel extends SchvalovatelPoziadavky {\n    public Riaditel() {\n        super("riaditel");\n    }\n    @Override\n    public void nastavitDalsiehoSchvalovatela(SchvalovatelPoziadavky dalsiSchvalovatel) {\n        this.dalsiSchvalovatel = dalsiSchvalovatel;\n    }\n    @Override\n    public void posuditPoziadavku(String poziadavka) {\n        if(poziadavka == "ZVYSENIE_PLATU") {\n            System.out.println(poziadavka + " - " + meno + " schvalil poziadavku");\n        }\n        else {\n            super.posuditPoziadavku(poziadavka);\n        }\n    }\n}<\/code><\/pre>\n
Employee<\/strong>, Supervisor<\/strong>, Director<\/strong> are specific classes representing individual employees. Each of them can approve certain types of requests, but if they are not authorized for some of them, they will pass them on to the next approver in the chain.<\/p>\n
Main.java<\/u><\/strong><\/p>\n
import designpatterns.Riaditel;\nimport designpatterns.SchvalovatelPoziadavky;\nimport designpatterns.Veduci;\nimport designpatterns.Zamestnanec;\n\npublic class Main {\n    public static void main(String[] args) {\n        \/\/ Clanky retaze\n        SchvalovatelPoziadavky zamestnanec = new Zamestnanec();\n        SchvalovatelPoziadavky veduci = new Veduci();\n        SchvalovatelPoziadavky riaditel = new Riaditel();\n        \/\/ Vytvorenie retaze zodpovednosti\n        zamestnanec.nastavitDalsiehoSchvalovatela(veduci);\n        veduci.nastavitDalsiehoSchvalovatela(riaditel);\n        \/\/ Posudenie poziadaviek\n        zamestnanec.posuditPoziadavku("NAVSTEVA_LEKARA");\n        zamestnanec.posuditPoziadavku("DOVOLENKA");\n        zamestnanec.posuditPoziadavku("ZVYSENIE_PLATU");\n        zamestnanec.posuditPoziadavku("FIREMNE_AUTO");\n    }\n}<\/code><\/pre>\n
The main <\/em> method is to set up a chain of responsibility, create a hierarchy of individual employees and then consider the various requests. Each person tries to approve the request. If they cannot approve it, they delegate it to the next approver in the chain.  <\/p>\n
\"The
The output of this example.<\/figcaption><\/figure>\n
Conclusion<\/h2>\n
The Chain of Responsibility<\/strong> design pattern is used in software design when we want to achieve a flexible way of processing requests, rather than creating a rigid link between the sender and the processor of the request and passing it to a chain of objects for processing.<\/p>\n
We have prepared the files with the above example in the form of code that you can run directly in Java. Download the Java Chain of Responsibility<\/strong> code here<\/a>.<\/p>\n
If you’re a Java developer<\/a> looking for work, check out our employee benefits<\/a> and respond to our job offers<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":"
What is the Chain of Responsibility design pattern and what is it for? Read our new article and download the sample code.<\/p>\n","protected":false},"author":14,"featured_media":2399,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[57],"tags":[],"class_list":["post-2969","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-java"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/posts\/2969","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/comments?post=2969"}],"version-history":[{"count":4,"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/posts\/2969\/revisions"}],"predecessor-version":[{"id":5265,"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/posts\/2969\/revisions\/5265"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/media\/2399"}],"wp:attachment":[{"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/media?parent=2969"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/categories?post=2969"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/msgprogramator.sk\/en\/wp-json\/wp\/v2\/tags?post=2969"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}