On 08 Mar 2011, at 17:38, Hans Lesmeister 2 wrote: > > +1 for making Page.onInitialize() non-final. Since 1.4.12 we have migrated a > lot of code moving construction of the component hierarchies to > onInitialize. We are really very happy with the way it is now in 1.4. > > -1 for throwing an exception if add(..) is called from within a constructor > (but maybe logging a warning instead?)
This is a valid vote if we can come up with a way of not having random failure side-effects from mixing the two (which is the whole reason the the issue exists in the first place), without a final onInitialize and an exception in add(). If such a solution is not suggested in this thread, we're gonna need either a final onInitialize or an exception in add(). You can't have your cake and eat it too. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
