You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changes the description of the template method pattern (as discussed in Issue1099) (iluwatar#1101)
* Declares the template methods as final
* Extends the description of the template method pattern
* Removes the final declarations (this was done in another branch)
* to implement the invariant parts of an algorithm once and leave it up to subclasses to implement the behavior that can vary
24
25
* when common behavior among subclasses should be factored and localized in a common class to avoid code duplication. This is good example of "refactoring to generalize" as described by Opdyke and Johnson. You first identify the differences in the existing code and then separate the differences into new operations. Finally, you replace the differing code with a template method that calls one of these new operations
25
26
* to control subclasses extensions. You can define a template method that calls "hook" operations at specific points, thereby permitting extensions only at those points
Method `GenericServlet.init(ServletConfig config)` calls the parameterless method `GenericServlet.init()` which is intended to be overridden in subclasses.
34
+
Method `GenericServlet.init(ServletConfig config)` is the template method in this example.
31
35
36
+
## Credits
32
37
*[Design Patterns: Elements of Reusable Object-Oriented Software](http://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612)
0 commit comments