Despite the repository strategy choosen, I agree with: -----Mensagem original----- De: Stephen McConnell [mailto:[EMAIL PROTECTED]
> I'm not convinced. Before such a vision is realistic we need to have a > *single* avalon component contract. What that means is that we don't > have ECM component and Forress components and Phoenix components and > Merlin components. It means we have *one* Avalon component model backed > by a conformance test suite provided by Avalon. I believe in a spec, even a single page spec and the idea of a test suite is really good. It won't be a J2EE burocracy - thats not the intention - but it is necessary. <personalopnion> I think its very hard to go on supporting different containers, and is even hard to bet in only one container. Every container has its pros and cons. If we got a container 'a la carte' we could live peacefully with only one. </personalopnion> hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
