This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Howdy, recently I have had the opportunity to see a very unusual Java design pattern in action (if it is indeed a design pattern).
Attempts to Google this come up short.
The pattern in question is: an Abstract class that extends a Concrete class and implements Runnable.
The concrete class implements a couple of additional Interfaces.
The code I'm referencing is in a Java web app that is current production code and is running!
My question is twofold:
Is there a name or type of so-called Java design pattern that can be attached to the description above.
If this is a know design pattern what are the overwhelming reasons to use such a pattern or what are the advantages/disadvantages to using the pattern described above.
Yet some, not wise, go to the other side of the globe, to barbarous and unhealthy regions, and devote ten or twenty years, in that they may live,-that is, keep comfortably warm,- and die in New England at last. Henry David Thoreau - Walden - 1845