The performance page suggests hand building XSPs: Consider turning your XSPs into Generators by hand and call them directly. Of course you don't need to do this for all pages, but it's recommended to it for those which are heavy loaded. You can try it this way: Cocoon will compile your XSP's into Java classes (see tomcat/work/..../org/apache/cocoon/www/my_xsp.class). After that, add the generated Generator to the Sitemap:
<map:generator type="myXSP" src="org.apache.cocoon.www.my_xsp"/> And use it: <map:generate type="myXSP"/> Is the xsp dependency checking so expensive that this it worth the maintenance cost is incurs? Is there more going on that just stat()ing the xsp file and the logicsheet it references? Is there a build-time option to precompile XSPs without doing it by hand? Thanks, Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
