Re: Why Template Method instead of Strategy in Commons Chain?

[Erik Weber]

I think it's probably usually good to question Template when the 
realization of it comes via class inheritance.

However, I'm confused. I read Bill's article (first pass anyway -- and 
I'm new to Commons Chain), and I'm still not seeing where exactly 
Template is implemented in Commons Chain. He introduces Template and 
then seems to say that while Template is still used, its detriments are 
mitigated. But I need help understanding exactly where it is used in the 
first place. (I'm not making the connection between the first code chunk 
and the following ones.) Only then will I be able to assess the question 
of whether Strategy would be better (or would even solve the same problem).

Here's a diagram of Template:
http://www.dofactory.com/Patterns/PatternTemplate.aspx
And here's a diagram of Strategy:
http://www.dofactory.com/Patterns/PatternStrategy.aspx
Could you plug the Commons Chain classes (existing or proposed) into an 
illustration (verbal will do) for me so I can better understand the debate?

Thanks,
Erik
Dakota Jack wrote:
I inquired why the Template Method pattern is being used with Commons
Chain instead of Strategy, but never got an answer.  Given that the
choice seems so problematic, that surprised me.  Is that (no response)
because there is no answer, or because it is a closed shop of ideas in
open source, or because there is no time to consider such a stupid
idea, etc.?
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]