You can inject the ComponentSource into an ApplicationInitializer and obtain the page by name. There's some other cleanup I can't research now.
It would be interesting to know exactly what is taking so long ... I think you may find it isn't until you reference your _user field that there's a delay, partly to set up the many necessary services, but also to create the HttpSession, which can be time consuming in some servers. On 9/13/07, Angelo Chen <[EMAIL PROTECTED]> wrote: > > > Hi Howard, > > I'm quite ok with T5's speed when comes to page display first time, but it > is really slow when a page contains : @ApplicationState private > SessionData > _user; loaded first time. Is there a simple way to pre-load that page? I > know the page name, dont have to be generic. > > > Howard Lewis Ship wrote: > > > > 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: > >> > >> > > -- > View this message in context: > http://www.nabble.com/How-to-init-T5-pages-on-deployment----1st-few-hits-would-be-faster-tf4437654.html#a12665752 > 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
