Hi!
Yes.. I think you can configure whether it shows stacktrace or is a
sensible page.
**
Martin
2011/2/24 Setya :
>
> Hi,
>
> I'm not sure I understand what you mean. I've set the error page via
> IApplicationSettings#setPageExpiredErrorPage
>
>
> Setya
>
>
> Martin Makundi wrote:
>>
>> Hi!
>>
Hi,
I'm not sure I understand what you mean. I've set the error page via
IApplicationSettings#setPageExpiredErrorPage
Setya
Martin Makundi wrote:
>
> Hi!
>
> Have you set pageexpirederrorpage->login?
>
> **
> Martin
>
> 2011/2/24 Setya :
>>
>> Hi all,
>>
>> What does actually happen when
Hi!
Have you set pageexpirederrorpage->login?
**
Martin
2011/2/24 Setya :
>
> Hi all,
>
> What does actually happen when Wicket throws page expired ? We're always
> getting this when user logs in to our application for the 1st time.
>
> Some facts that might be related to the problem:
> 1. The a
Hi all,
What does actually happen when Wicket throws page expired ? We're always
getting this when user logs in to our application for the 1st time.
Some facts that might be related to the problem:
1. The application was deployed on clustered Glassfish fronted by
Apache+mod_jk as load balancer.