Felix Knecht wrote:
>> Thinking a little bit more about it, this will create problems for the
>> sitemap components that I have tried to make configurable both as an
>> Avalon component and a ordinary Spring bean. Consider the file
>> generator, it is a poolable component and will probably be served
>> through some proxy that the Avalon bean post processor adds. But in
>> the Spring configuration I made it a prototype scoped bean. As it has
>> been like this for some time it seems like it works, burt I would
>> guess that it consumes unnecessary resources.
>>
>>> But I really think, if you develop a "plain" spring bean, that you
>>> shouldn't use any avalon interfaces.
>>>
>> Exactly, and I start to think that my suggestion that we should keep
>> the Avalon configurabillity of sitemap components wasn't such a good
>> idea. It seem to create more problems than it solves.
>>
>> I suggest that when Springifiing components, we just remove the Avalon
>> stuff.
>>
>> WDYT?
>
> +1
lovely, less work for me :)
and seriously: +1
--
Leszek Gawron http://www.mobilebox.pl/krs.html
CTO at MobileBox Ltd.
|