On 07.07.2004 22:42, Christian Rosenberger wrote:
I have a question regarding the jars in WEB-INF/lib. Is there a list, which jars are needed by which block? I know the minimal webapp wiki documentation, but it isn't helpful regarding which jars I have to use and which jars I could remove. (commenting out all blocks at build time is not an option... ;-) )
Why is excluding blocks at build time not an option? That is why the blocks exist at the moment.
At startup the webcontainer/appserver is loading all jars. (currently approx. 30-40MB). If I could minimize jar loading, the memory usage of Cocoon would be much lesser than it is at the moment.
No, having the JARs in WEB-INF/lib does not increase the memory. This would only happen if for example every class would be instantiated. So the classloader "only" needs more time when searching a class.
Currently the application server uses about 100-120MB of memory while using Cocoon. With other web application the memory usage is about 60-80MB. I think a lot of these memory is taken by the jars at startup. Any hints which jars are not required?
When excluding blocks at build time you will also prevent some things from being instantiated and so reduce the memory foot print. If that's still not an option for you, you can have a look into each block's lib dir to see which JAR comes from which block. Some of the JARs in lib/optional could also be removed, but they are needed from multiple blocks. By removing the JARs from hand (instead of using the blocks build system) you also can break your Cocoon instance as (as I wrote above) the blocks also add their configuration to cocoon.xconf and cocoon.roles which can result in instantiations of classes - if the class is missing you will get a NoClassDefFoundError. Be sure, using the build system is by far the appropriate solution.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
