> -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED] > > More importantly it is meant to be stable and well tested.
Yes, but it only needs to be so when it is actually released. While we are still developing the next version the code will by necessity be unstable and untested. Maybe you mean that with a release this close, no new code should have been checked in? > I hope you are not suggesting this is good programming practice? It is. If you can do it, it is very good - and if Java had Eiffel's support for pre- and post-conditions, you would. Or rather, the Servlet interface would have declared those preconditions for you and you would have inherited them for free. The ComponentUtil/AbstractComponent/ComponentState classes gives us second-best: A way to get preconditions with minimal coding. > So write a base TestCase class that can use to test the container. That is a good idea, irrespective of ComponentUtil/etc. I think the FullLifecycleComponent does it. /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
