OK. Best-practice-thing. Technically this helps me writing my services since I do not have to take care that my LC-interfaces are called in the correct sequence (as it is done in the DwA with several status flags) - right?
you don't want to be doing that. It is unneccessary overhead (as the container guarantees things are working properly anyway) which you want to use for debugging (of containers) only. If you need to do that, there's
http://cvs.apache.org/viewcvs.cgi/avalon-excalibur/testcase/src/java/org/apache/avalon/excalibur/testcase/ComponentStateValidator.java
(only available through cvs ;) which isolates it rather nicely. BTW, if anyone feels like updating Developing with Avalon to reflect this best-of-practice, patches welcome! :D
cheers,
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
