On Fri, 20 Dec 2002 12:56, Adam Murdoch wrote: > Goodness. I just want to get the stuff I need for my component. Why is it > so hard? Why do I need to know all this stuff? Why isn't there a single > method that gives me what I need? What benefit do I get out of all these > methods and contracts?
The same benefits you get when you asked this last time scalability and flexibility. Some component styles don't implement Contextualizable or Serviceable/Composable or Configurable/Parameterizable or whatever. Others do different things at different stages (ie some containers have replaced Comopsable/Serviceable with their own custom lookup lifecycle). > Whatever you happen to call this antipattern, taking a single real concern > and dividing it into several artifical concerns causes problems. I don't believe anyone has shown that they are "artifical concerns". -- Cheers, Peter Donald -------------------------------------------- Beer is proof that God loves us and wants us to be happy. -- Benjamin Franklin -------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
