> > But I also don't have a solution at hand; if we cannot come to a single > > implementation, probably it's because we still don't know how to do it. > > Yes, that's possible. > Now, we could try to make a single implementation where all agree on > and only if this does not work - we can start several ones. > My perception is, that it is possible to reach a wide consensus on > this.
(Vote) -1 I do not believe it is necessary to make the containers we have compatible at anything other than Avalon-Framework-Interface level. If we strive for compatibility on component-lacing (XML, properties, whatever) we will find some other team does not honor the chosen lacing team an delivers a container with a twist. This could be BEA, Pramati, JBoss, Catalina, OpenEJB, Lutris. It could be some University in Bangalore or Manila. We cannot contain the container landscape; we'd be foolish to try. There are thing people are imagining now that will impress the socks off us when released. Better to concentrate on our core product -> Avalon Framework's interfaces. Embrace the multi-container world!! - Paul __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
