On Mon, 11 Feb 2002 19:28, Paul Hammant wrote: > Our three choices again, with Gerhard's too. > > (1) Change Component to Object for lookup method
-1 - backwards incompatible > (2) Create a new method in the same ComponentManager interface > > variations : "lookup2", "resolve" -1 - backwards incompatible > (3) Clone a set of interfaces & exceptions into a new package, either > with the same names, or not. > > (4) Create a new interface in the existing package > > e.g. GenericComponentManager either of those are backwards compatible so fine. > PD> If Sun jumped off a cliff would you do it too ? > > No, but I think that a "2" suffix is not so objectionable to get around a > return type issue. perhaps. I wont veto it but I really dislike it. Consider LogEnabled vs Loggable2 - which do you think is easier to understand/read. :) So +1 to doing something backwards compatible in framework4.x If this aint accepted then we can prototype framework5 relatively fast and even keep it compatible with framework4.x by putting it in a new package. ie we could go back to org.apache.framework -- Cheers, Pete Doubt is not a pleasant condition, but certainty is absurd. -- Voltaire -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>