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 :)
Vadim
