cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <>
Subject Re: svn commit: r522901 - in /cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-impl/src/main: java/org/apache/cocoon/caching/impl/ resources/META-INF/cocoon/spring/cocoon-pipeline-impl-cache.xml
Date Thu, 29 Mar 2007 19:14:02 GMT
Carsten Ziegeler wrote:
> Vadim Gritsenko wrote:
>> Last I checked, and since 2.2, it is impossible (or just really hard?) to start 
>> up cocoon without servlet context and related objects, which means it gotta be 
>> deployed and started as part of the webapp. If that is the case, IMHO there is 
>> no good reason to have it as part of the shared classloader.
> Yes, that's true for "the framework Cocoon" - but perhaps not for the
> various parts/components.

Ok, that's good reason.

>>> As most of our components are singletons anyway, there isn't any memory
>>> problem here.
>> There are some generated poolable wrappers, IIRC - those aren't singletons and 
>> do represent good chunk of components (pipelines and all direct sitemap components).
> Yes, sooner or later we hopefully get rid of these, too :)

Until then those wrapper could use static logger (if they need any), for 
efficiency :)


View raw message