Hi Howard,
The deplay happens before I refer to _userExists, just displaying the page
takes a long time, you can see from the code below, the _user field is
referred to in onSuccess which is after the page display:
@ApplicationState
private SessionData _user;
private boolean _userExists;
String onSuccess() {
}
Howard Lewis Ship wrote:
>
> 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.
>>
--
View this message in context:
http://www.nabble.com/How-to-init-T5-pages-on-deployment----1st-few-hits-would-be-faster-tf4437654.html#a12666574
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
