At 12:00 3/5/01 -0700, Craig R. McClanahan wrote:
>On Thu, 3 May 2001, Michael L. Heuer wrote:
>> apologies if this is seen as trolling, but aren't there implementations of
>> logging kits, thread and object pools, and other goodies, all nicely
>> wrapped in 'Separation of Concerns' interfaces allowing for maximum
>> pluggability and configurability of a system, already in the jakarta
>> Avalon project?
>>
>> > http://jakarta.apache.org/avalon/framework/api/index.html
>>
>> michael
>>
>>
>>
>
>There definitely are -- as Peter Donald never hesitates to point out :-).
Another thing that pesky guy points out that the components are largely
framework agnostic - it's amazing how you never point out that point?
Selective memory eh ? ;)
>However, if you look at the code itself, it's the "wrapped in 'Separation
>of Concerns' interfaces" that causes one to pause. To use these classes,
>you have to buy into Avalon as a *framework*, not just as a source of
>components. If you are going to use Avalon anyway, that's a great
>convenience -- if you're not, then you are faced with having to deal with
>configuration and lifecycle issues differently for the Avalon-originated
>components versus the others.
Thats quite false and you know it ;)
The vast majority of excalibur (the component repository) is framework
agnostic. The part that isn't framework agnostic (namely pooling code) will
be enhanced or complimented post release. SO what were you yammering about
again ? Ahh yes - NIH - I remember now ;)
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
