gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
java-design-patterns/execute-around
History
Narendra Pathai 2aa9e78ddd
Minor refactorings and code style changes (#807) 
* Made minor changes in some patterns such as removed throws clause where not needed, changed incorrect order of arguments in assertEquals

* Minor refactorings and code style changes. 1) Removed several use of raw types 2) Removed unnecessary throws clauses 3) Used lambda expressions wherever applicable 4) Used apt assertion methods for readability 5) Use of try with resources wherever applicable 6) Corrected incorrect order of assertXXX arguments

* Removed unused import from Promise

* Addressed review comments

* Addressed checkstyle issue
2018-10-23 13:45:41 +05:30
..
etc
#190 Remove urm plugin
2017-11-28 20:55:52 +02:00
src
Minor refactorings and code style changes (#807)
2018-10-23 13:45:41 +05:30
pom.xml
Set version for next development iteration
2018-09-30 21:05:57 +03:00
README.md
#190 Remove pumlids from readmes
2017-11-28 21:28:53 +02:00

README.md

layout, title, folder, permalink, categories, tags
layout title folder permalink categories tags
pattern Execute Around execute-around /patterns/execute-around/ Other
Java
Difficulty-Beginner
Idiom

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

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.

Credits