I sure feel there is a big waste of Avalon code going on. The Avalon team is ALSO to blame on that... but is not alone.
On one hand I agree that it is plain stupid that some people do not even look at it just based on personal issues... ...but OTOH, Avalon still ties most components to the framework structure. I just have an ongoing discussion at the avalon-dev list about this kind of issues and it does not look like it is going to change. The last time I discussed this was on the "RE: Divergence from Avalon (was Re: [RT] Is Poolable Harmful?)" thread which is continuing on the "RE: Recapping Discussion on Component Accessing" thread. I still could not answer this last one (I really could not take the time for it during the last days) but it does not look good. All the arguments I made about removing a couple of interface dependencies (some of them just marker interfaces) in order to make it easier to use 3rd party components and to make Avalon components easier reuse without the framework seem to be ignored by Berin and Leo. Only Donald seems to keep an open mind about the issue. HOWEVER, lets not forget that Berin already offered to help breaking some of those dependencies on several Avalon components. IMO it is plain stupid that several components with a high potential for reuse are tied to the framework structure by a couple of interfaces that could easily be removed, as it happens with (just one example) the pool component. That scares potential users away. OTOH (again) it is silly not to use Avalon at least to steel the interesting bits instead of reinventing the wheel all over again. Even because the dependencies I mentioned are REALLY EASY to remove. (And, of course, I could be saying the same about Turbine, as Jon often remarks.) Maybe I am missing some high education principles but I see no reason why some of the highly reusable Avalon code is not reused. Even if the Avalon guys want to keep it tied (and this is not so clear as Berin attitude shows) I see no reason not to fork. So, what I really do not understand is the eternal wheel reinvention! =:o/ Have fun, Paulo Gaspar > -----Original Message----- > From: Sam Ruby [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 21, 2002 3:34 PM > To: Jakarta Commons Developers List > Subject: Re: AltRMI Tasks if anyone want to take them > > > Paul Hammant wrote: > > > > Excalibur people's hearts break a little (understandably) when this is > > proposed. Avalon was at one stage supposed to be useful, reusable, > > patterns based foundation code for server apps or servlet environment > > apps. I have never contributed much to Excalbur but can't help feeling > > loyal to my Avalon comrades..... > > One doesn't tend to find alternators for Dodge Caravans at a Ford > dealership. > > - Sam Ruby > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
