I was looking at the new ContainerManager. It is currently making use of the ComponentStateValidator to validate that the managed container is being started correctly.
I am 100% in favor of using the ComponentStateValidator in places where it is possible for a user, through the use of invalid code, attempt to initialize or use a component incorrectly. But in this case, the ContainerManager will be a core class and we know that it will always correctly follow the Component contracts when initializing the container. So I don't think it is really needed here. I might have missed something in the design though, :-) Cheers, Leif -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
