Gang,
I have just read through all of the Fortress discussion mails. There seems to be 2 major consensus (we can agree on) in there;
1. ECM/Fortress should stay with Apache. 2. ECM/Fortress users should not be abondoned.
I also get the feeling that there are many proponents of Fortress to 'live on', and if that true, we not do that...
I think I am more and more in favour of;
1. Apache Avalon = Component contracts.
2. Place Merlin & Fortress into subprojects of Avalon.
3. The Fortress gang rally a community around it to show that it is really live and well, and not just "hot air".
Yes, yes, yes...please, please, please! I cannot agree more!
I'll tell you one thing that I and many others have learnt while using Avalon and developing services for Keel. Every time we add a second and third implementation of a service, we find the need to change the service interfaces we created the first time around. It takes the sometimes opposing needs of different implementations, and the sometimes opposing views of the different developers, for the generic interface to materialize properly.
Shash
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
