cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Re: SimpleForm transformers
Date Wed, 10 Oct 2007 05:46:25 GMT
Joerg Heinicke wrote:
> On 09.10.2007 9:44 Uhr, Reinhard Poetz wrote:
>>>>> At CocoonGT we had some sort of agreement to create optional modules

>>> Please, no more modules. It is bad already as it is - adding *more* 
>>> modules only makes it worse. What's wrong with simply deprecating 
>>> them, with placing appropriate javadoc?
>>> +1 to move to -components, these are certainly not -core.
>> But this doesn't solve the problem that many components are loaded 
>> into the spring app context by default. Having them into a seperate 
>> module makes it easy to exclude them. But of course than you can run 
>> into the situation that you only need one of them and get them all 
>> loaded again :-(
> Why do you care that much about them? Of course they increase the memory 
> footprint but not for megabytes.

It's memory consumption and startup time which I'm worried about.

>> However, what we could do is introducing a rule that every *.opt.xml 
>> file in META-INF/cocoon/spring and META-INF/cocoon/avalon isn't loaded 
>> automatically but needs to be included explicitly.
> Don't make it too complicated with too many rules. There are already 
> many conventions to get stuff included. Now we want to add even more to 
> get it excluded again? I'd say don't fix it before there is the 
> requirement. spring-configurator can always easily be extended for such 
> a feature.

I think so too. I will do some tests when RC2 is out to find out if my concerns 
are valid at all. Thanks to all for sharing your thoughts.

Reinhard Pötz                            Managing Director, {Indoqa} GmbH

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair

View raw message