Reduced to the minimal term, here is the example of a method that we could refactor using the execute around pattern. The code is made more interesting by using the try-with-resources statement available in Java since version 7.
public static String processFileLimited(String filename) throws IOException { try (BufferedReader br = new BufferedReader(new FileReader(filename))) { // 1 return br.readLine(); // 2 } }1. We try to create a BufferedReader. At the end of the block, even in case of an exception, Java takes care of closing the resource. Neat.
2. This is the behavior we want to be parametrized.
Lambda is here our friend. Only a minor nuisance, we can't use a standard functional interface because here we should let our lambdas throw an IO exception, and in Java this should specified in the method signature.
@FunctionalInterface public interface BufferedReaderProcessor { public String process(BufferedReader br) throws IOException; }Given this interface, we can refactor the above method in this way:
public static String processFile(String filename, BufferedReaderProcessor p) throws IOException { try (BufferedReader br = new BufferedReader(new FileReader(filename))) { return p.process(br); } }The boilerplate is there unchanged, the actual behavior has been externalized. It should be user resposibility to provide something sensed to be done in. Here is a couple of different ways processFile() could be called:
ExecuteAround.processFile(FNAME, (BufferedReader b) -> b.readLine()); ExecuteAround.processFile(FNAME, (BufferedReader b) -> b.readLine() + '-' + b.readLine());As second parameter, I pass a lambda that in its body uses the BufferedReader to perform its job. A string is (implicitly) returned.
I have divided the code between the actual ExecuteAround class and its unit test. You can find both on GitHub.
Code and ideas are based on Java 8 in action, section 3.3 Putting lambdas into practice: the execute around pattern.
No comments:
Post a Comment