From 1fc15829ade98732e0debdf816896a5b9b66516b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ilkka=20Sepp=C3=A4l=C3=A4?= Date: Sun, 29 Mar 2015 21:44:05 +0300 Subject: [PATCH] Fixed link. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 13343121b..bad1ec15e 100644 --- a/README.md +++ b/README.md @@ -425,7 +425,7 @@ Behavioral patterns are concerned with algorithms and the assignment of responsi ## Execute Around [↑](#list-of-design-patterns) **Intent:** Execute Around idiom frees the user from certain actions that should always be executed before and after the business method. A good example of this is resource allocation and deallocation leaving the user to specify only what to do with the resource. -![alt text](https://github.com/iluwatar/java-design-patterns/blob/master/execute-around/etc/execute-around.png "Execute Around") +![alt text](https://github.com/iluwatar/java-design-patterns/blob/master/execute-around/execute-around.png "Execute Around") **Applicability:** Use the Execute Around idiom when * You use an API that requires methods to be called in pairs such as open/close or allocate/deallocate.