> From: Artur Bialecki [mailto:[EMAIL PROTECTED]] > > Can you explain how this makes things faster, I assume > XSPs are not convereted to Java and complied each time > I access given XSP. Is the performance difference in > sitemap processing, cache lookups, etc.
One is serverpages generator overhead (which is not huge), and another is that the XSP pages are compiled into poolable generators, and pool is created with default values for minimum and maximum sizes. If you want to size pool for your particular XSP, you turn it into generator. > If so how much. Measure and tell us. Vadim > Thanks, > > Artur... > > > -----Original Message----- > > From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, March 26, 2002 2:11 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Turning XSPs into Generators > > > > > > > From: Michael Zehrer [mailto:[EMAIL PROTECTED]] > > > > > > Hi list, > > > > > > reading the Performance Guide Draft, it sems to me that turning XSPs > > > into Generators is a good idea, is there some general way how to do > > > this? Any tips, templates? > > > > Once you run XSP once, Cocoon will compile them into Java classes (see > > tomcat/work/..../org/apache/cocoon/www/my_xsp.class). After that, add > > generator to the sitemap: > > > > <map:generator type="myXSP" src="org.apache.cocoon.www.my_xsp"/> > > > > And use it: > > > > <map:generate type="myXSP"/> > > > > Vadim > > > > > > > > Cheers, Michael --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
