Hi Peter, > I'm not sure what DwA is an acronym for.. but yes.
DwA references the fine, but somewhat outdated tutorial "Developing with Avalon". The classes in the code examples have internal markers keeping their state and they throw errors, if the container calls the component in wrong LC order. >The container will > call your LC-interfaces in the correct order, the proxies > will prevent > people from doing > > Object o = ServiceManager.lookup( O.ROLE ); > > ((Initializable)o).initialize(); > > (or more drastically, reconfiguring your component at runtime behind > your back!) So, this is the best reason for system stability. While the developers could now omit the internal state checks, it might me good to keep them for better reusability ... wasn't there any CheckUtil class? Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
