> -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED] > > a) a dodgy container > or > b) evil clients who can get direct reference to component > > if (a) is true then it should be fixed not worked around.
True, it should be fixed in the container. There is no reasonable way to survive the handling of a container that calls the methods in the wrong order. And that is just the point: Fail early. Do not wait and fail later. If the container is dodgy, the component can help by failing fast, much like the Iterator classes. Here's a patch for some refactoring of AbstractComponent. /LS
avalon.diff
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
