On Thursday 05 February 2004 06:26, Leo Simons wrote: > What is *not good* is /other/ classes (other than subclasses) calling > these methods. If its not a lifecycle method or a work interface method, > you'll probably want to make the method private, or protected.
I commonly find myself in a situation where a cluster of classes in the same package together fulfill the Service Interface, in which case some of the "unexposed" methods are package protected, the rest private. IOW, typically only the Service Interface and Life Cycle methods are public. And in my case, I hardly ever have 'protected' in COP scenarios, SoC quickly falls apart with inheritence. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
