Should be possible at startup; there's an ApplicationInitializer chain of command.
You have to dive into the internals; ComponentClassResolver would need a method that could provide the names of all pages. It knows, but doesn't currently have an API to share that information. Armed with the page names, you would just have to make a bunch of calls to ComponentSource.getPage(), then perform a little bit of cleanup work (so that the acquired pages go back into the page pool). On 9/13/07, Martin_S <[EMAIL PROTECTED]> wrote: > > > Tapestry 5 currently is slow when a user hits a page for the first time. > Does anyone know how to make T5 create all page instances at deploy time > in > Tomcat? For example, the Hibernate project suggests using a > ServletContextListener to create a SessionFactory. Something similar would > be great in T5 to get a better response time when the first user hits a > page. > I know just doing requests from a utility class would be a quick-and-dirty > workaround, but surely there has to be a better way. > -- > View this message in context: > http://www.nabble.com/How-to-init-T5-pages-on-deployment----1st-few-hits-would-be-faster-tf4437654.html#a12660957 > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind
