Here I go, exposing my ignorance of patterns. (No, I have not read the "Gang of Four" book on patterns or any other such scriptural reference.)
Jack -- Exactly what would have to change in the current RequestProcessor for you to consider it a "Template" pattern? -- Jeff On Wed, 9 Mar 2005 06:41:23 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote: > TEMPLATE! METHOD! TEMPLATE! METHOD! TEMPLATE METHOD! Scheesch! Help! > > The RequestProcessor is NOT difficult to understand. It is a java > CLASS, neither an abstract class nor an interface, which has one > principal public method, viz. process(...) which involves a lot of > code which is further broken down into parts delivered seriatim by > eighteen protected methods. There are also three protected supporting > methods and two public methods for initialization (init(...)) and > destruction (destroy()). The "structure" of the class, with the > processing in the process(...) method is "shown" below. -- Jeff Beal Webmedx, Inc. Pittsburgh, PA USA --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
