I believe the slowness you're seeing at initial page load isn't so much the class enhancement (and not the compilation, of course, since that's already done); it's the parsing and initialization of the component graph. There is a way to trick Tapestry into preloading all the pages on first access... check a couple of old threads here: http://marc.theaimsgroup.com/?l=tapestry-user&w=2&r=1&s=preload&q=b
But it's cumbersome and imperfect and it turns out not to be a big benefit. It makes the first access of the app a lot slower, in exchange for a small speed-up on the first visit to each page. We did it that way for a long time and stopped it. The one nice thing about it was the syntax checking of all the pages at startup, which is handy in development when you make a global change and don't want to visit all the pages manually. You could achieve the same benefit (and more) by using an http tester tool (JMeter, for example) to visit all your pages. seng kim khong wrote: > Hi All, > > If I not wrong, the page class in tapestry is an abstract class and it > will > be extends in run time and generate instance based on that class on > the fly. > But this will let the 1st time loading of tat page become slower. > > So, I would like to check out is it tapestry got provide any script to > compile (maybe I use the wrong keyword) the page class 1st before the > user > request to that particular page to make it can be run faster. This > concept > is like the jspc which can turn the jsp page to be servlet 1st before > user > request to that paricular jsp page. > > Thank you in advance for any info. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
