On Fri, 21 Jun 2002, Nicola Ken Barozzi wrote: > Remy, I hear you. > Current Avalon is what you say. > Next Avalon will be what it was supposed to be in the first place.
I think next avalon should start by looking for a problem to solve before proposing the solution to all the problems :-) And it should start looking at what APIs are already used ( JMX, JNDI, etc ). > > Also, most of the utility provided by Avalon are available from the > > commons without any string attached, and/or are of a better quality. > > Utilities provided by Avalon are lifecycle management and component > reusability+management. I don't think we have problems with the lifecycle management or component management ( for the last JMX seems to solve the problem ). > Could you kindly summarize the things that Avalon needs to do before you > would even consider taking it in consideration as a framework? I suppose finding the problem to solve would be a good first step. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
