I really don’t see the point in them… code is often simpler without them, and if you want to offer standardized logging or exception handling or transaction management or whatever within that pipeline, you can usually just put that behavior in an aspect and apply it to a simple method which only contains the code that normally would’ve been in the pipeline.

Btw, i don’t think template methods in general are bad… i do use them when they come in handy, but i only use it when i want to delegate a small piece of behavior to a derived class. Never to ‘force’ a specific execution pipeline. When i need to implement too many template methods, i always feel there’s gotta to be a better way and that the necessity of the template methods might indicate that i’m working with a wrong level of abstraction.