Leo Simons wrote:
Hi peeps,
lots of code that assumes a 'hostile' environment keeps track of the lifecycle and ensures it is correctly followed. Part of the defensive coding paradigm I guess. Often not to accurately, though :D
I wrote a class org.apache.avalon.framework.State which codifies this correct behaviour. The proposal is that it is included in framework 4.1.4. I've yet to test it (and write the testcase).
comments?
We already have one in Excalibur Util. THe ComponentStateValidator, and its associated test cases.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
