Hi, Have been reading the excellent artifact written by Berin Loritsch on "Developing with Avalon" .
A query derived from there. (from page 32). Why does an individual component have to be made to write code so as to honor a policy of lifecycle management; which is that methods calls like configure(),compose() ...etc has to be called ONCE and only ONCE during components lifetime and we have to write code to keep track of that with boolean flags indicating whether the method was called or not. I mean why doesn't the LifeCycleHelper class itself keep track about the number of times the component's lifecycle methods . This would also remove that small mess of boolean flags created in each component to keep track of this behavior. (private boolean initialized = false;private boolean disposed = false; etc.... ) Is this way of tracking of *valid* calls made to the components outside the component , a poor design.? Vinay. __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
