Bryan Lewis <bryan <at> maine.rr.com> writes: > In our old Engine we preloaded all the pages at the first request, to > check that there were no errors and to avoid delays later. We hooked > into the startup sequence by overriding createVisit(). That method's > gone now, and so are others like createGlobal() and setupForRequest(). > I tried a couple of probably-silly approaches -- hooking > requestInitialized() and even service() -- but I can't see a way to > do this in a place where I can get both a requestCycle and the > servletContext.
If the first request is always for the page service, you may extend the PageService class and override its service() method. In the serivce() method you can get access to the request cycle and the servlet context (through injection). Then make a contribution to the tapestry.services.ApplicationServices configuration point. -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
