Skip to main content

Behavioral Patterns : Command


Properties:
-          Encapsulates  set of actions to achive a task.
-          A command can be executed to complete a task without need to know what it does.


Implementation:
-          Command interface declares method or methods that encapsulates actions.
-          Receiver is passed to a command object and does the actual work that is specific to certain task.
-          Concrete Command class defines actual steps to achieve a certain task.
-          Invoker invokes the commands objects.
-          Client creates command objects and passes to invoker for execution.

Java Standard Library Implementations:
-          java.lang.Runnable
-          javax.swing.Action


Example Usage:

class ConcreteCommand extends Runnable{
    Reveiver _receiver;
    public ConcreteCommand(Reveiver _receiver){
        this._receiver=receiver;
    }
   
    public void run(){
        _reveiver.doAction();
        System.out.println("Action is completed!")
        _receiver.cleanUp();
    }
}

public static void main(String[] args){

    // invoker is responsible for executing the commands
    ExecutorService executerService = new ThreadPoolExecutor(
        5, 5, TimeUnit.MINUTES,new ArrayBlockingQueue<Runnable>(5, true));
   
    //receiver does the actual work
    Receiver receiver = new Receiver();
   
    // Command object is created with receiver object passed to it
    Runnable command = new ConcreteCommand(receiver);
   
    // command is invoked
    executerService.execute(command);

    executerService.shutdown();
}

Comments

Popular posts from this blog

Obfuscating Spring Boot Projects Using Maven Proguard Plugin

Introduction Obfuscation is the act of reorganizing bytecode such that it becomes hard to decompile. Many developers rely on obfuscation to save their sensitive code from undesired eyes. Publishing jars without obfuscation may hinder competitiveness because rivals may take advantage of easily decompilable nature of java binaries. Objective Spring Boot applications make use of public interfaces, annotations which makes applications harder to obfuscate. Additionally, maven Spring Boot plugin creates a fat jar which contains all dependent jars. It is not viable to obfuscate the whole fat jar. Thus obfuscating Spring Boot applications is different than obfuscating regular java applications and requires a suitable strategy. Audience Those who use Spring Boot and Maven and wish to obfuscate their application using Proguard are the target audience for this article. Sample Application As the sample application, I will use elastic search synch application from my GitHub repository.

Hadoop Installation Document - Standalone Mode

This document shows my experience on following apache document titled “Hadoop:Setting up a Single Node Cluster”[1] which is for Hadoop version 3.0.0-Alpha2 [2]. A. Prepare the guest environment Install VirtualBox. Create a virtual 64 bit Linux machine. Name it “ubuntul_hadoop_master”. Give it 500MB memory. Create a VMDK disc which is dynamically allocated up to 30GB. In network settings in first tab you should see Adapter 1 enabled and attached to “NAT”. In second table enable adapter 2 and attach to “Host Only Adaptor”. First adapter is required for internet connection. Second one is required for letting outside connect to a guest service. In storage settings, attach a Linux iso file to IDE channel. Use any distribution you like. Because of small installation size, I choose minimal Ubuntu iso [1]. In package selection menu, I only left standard packages selected.  Login to system.  Setup JDK. $ sudo apt-get install openjdk-8-jdk Install ssh and pdsh, if not already i

Java: Cost of Volatile Variables

Introduction Use of volatile variables is common among Java developers as a way of implicit synchronization. JIT compilers may reorder program execution to increase performance. Java memory model[1] constraints reordering of volatile variables. Thus volatile variable access should has a cost which is different than a non-volatile variable access. This article will not discuss technical details on use of volatile variables. Performance impact of volatile variables is explored by using a test application. Objective Exploring volatile variable costs and comparing with alternative approaches. Audience This article is written for developers who seek to have a view about cost of volatile variables. Test Configuration Test application runs read and write actions on java variables. A non volatile primitive integer, a volatile primitive integer and an AtomicInteger is tested. Non-volatile primitive integer access is controlled with ReentrantLock and ReentrantReadWriteLock  to compa