Timeline for Design pattern for wrapping logging around execution
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2015 at 12:11 | comment | added | Make42 | It is not that I absolutely want to use a pattern (just a bit ;-)), but that the code right now is so moist (in the sense of "not DRY"). The main issue here is obviously that functions can't be given as arguments as in functional programming in Java up until 7 (and I can't use Java 8 for business reasons). @Spotted | |
| Oct 3, 2015 at 12:10 | comment | added | Make42 | I have not quite understood the template pattern, but I'll give it another go soon. In the meantime: How about using the Command Pattern? I gave an answer using a Command Pattern - please comment! | |
| Oct 2, 2015 at 13:40 | history | edited | Spotted | CC BY-SA 3.0 | deleted 2 characters in body |
| Oct 2, 2015 at 13:35 | history | edited | Spotted | CC BY-SA 3.0 | added 76 characters in body |
| Oct 2, 2015 at 13:29 | comment | added | Spotted | @user49283 I also have updated my answer | |
| Oct 2, 2015 at 13:27 | comment | added | Spotted | @user49283 Why do you want to call super.execute() as this method is abstract ? | |
| Oct 2, 2015 at 13:25 | history | edited | Spotted | CC BY-SA 3.0 | added 1498 characters in body |
| Oct 1, 2015 at 16:21 | comment | added | Make42 | Your solution is not complete - maybe due to my bad explaining. I'll add information in the question. | |
| Oct 1, 2015 at 16:19 | comment | added | Make42 | Would it work to omit the origin attribute and write super.execute(); instead of origin.execute();? | |
| Oct 1, 2015 at 13:47 | history | answered | Spotted | CC BY-SA 3.0 |