cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <>
Subject Re: [RT] what about cocoon on a diet?
Date Sat, 16 Apr 2005 16:32:00 GMT
> Modularizing is just a matter of reorganizing Jars, which proguards
> doesn't care about :-)

Well ...of course you would have to leave some modules
out of the analysis ...that's the idea ;-)

> To use a shrinker efficiently, you have to tell him all class names that
> are loaded dynamically (can be automated by analyzing cocoon.xconf and
> the sitemap) and the entry points of your application (i.e.
> CocoonServlet.service).

IIRC there is also BCEL example where you point to a certain
directory full of jars. It will anaylize the jars. Track
intanciations and references etc. The transitive hull of
the call graph and the references then can be used to
determine what's really needed.

So basically the question is how you want to assemble
your tailored version of cocoon. Having a more modular
kernel would be one approach...


View raw message