Hi Oleg, > I have a fairly simple rule to deal with the problem: inject requisite > dependencies for which no reasonable default impl can be created through > a constructor, optional dependencies - through setters. With a few > notable exceptions this approach works well for me.
I'm fine with setters in the implementation class. I just wouldn't want them in the interface. Since I don't use DI frameworks, my take on setters is: if you don't want an attribute to change during the lifetime of the object, then don't provide a setter. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
