Skip to main content

Behavioral Patterns : Visitor


Properties:
-          Used when it is necessary to execute actions on members of an object structure (e.g. collections, hierarchical structures, composite structures).
-          Separates algorithm of the actions from the object structure members. So that new algorithms can be modified easily.
-          This pattern relies on polymorphic calls and helps to follow open/closed principle.
-          Another advantage is that visitor objects may be statefull.
-          One disadvantages is, while it is easy to add new visitors, it is difficult to add new observable objects.

Implementation:
-          Visitor interface declares visit methods. For each  ConcreteVisitable object a separate overridden visit method should be declared.
-          ConcreteVisitor implements visitor.
-          Visitable interface declares the accept method to which visitor instance is passed.
-          ConcreteVisitable implements visitable interface and defines accept method which executes the visitor.
-          ObjectStructure contains visitable objects. Visitable objects are iterated and visitor is passed.
-          Double Dispatch: Refers to how visit method to invoke is selected. First dispatch is selecting the accept method, which is determined by static type of visitor and dynamic type of visitable. Second dispatch is selecting the visit method, which is determined by dynamic type of visitor and static type of visitable.

Java Standard Library Implementations:
-          java.nio.file.FileVisitor
-          javax.lang.model.element.AnnotationValueVisitor
-          javax.lang.model.type.TypeVisitor

Example Usage:

Path start = Paths.get(".");
Files.walkFileTree(start, new SimpleFileVisitor<Path>() {
 @Override
 public FileVisitResult visitFile(Path file, BasicFileAttributes attrs)
     throws IOException
 {
     Files.delete(file);
     return FileVisitResult.CONTINUE;
 }

 @Override
 public FileVisitResult postVisitDirectory(Path dir, IOException e)
     throws IOException
 {
     if (== null) {
         Files.delete(dir);
         return FileVisitResult.CONTINUE;
     } else {
         // directory iteration failed
         throw e;
     }
 }
});

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