On Tue, May 15, 2012 at 9:10 AM, Guillaume Smet
wrote:
> Hi Martin,
>
> On Tue, May 15, 2012 at 8:44 AM, Martin Grigorov wrote:
>> Since https://issues.apache.org/jira/browse/WICKET-4014 (Wicket 1.5.1)
>> Wicket is able to handle automatically page expiration for mounted
>> pages. I.e. if the use
Hi Martin,
On Tue, May 15, 2012 at 8:44 AM, Martin Grigorov wrote:
> Since https://issues.apache.org/jira/browse/WICKET-4014 (Wicket 1.5.1)
> Wicket is able to handle automatically page expiration for mounted
> pages. I.e. if the user clicks a link and the page is already expired
> then depending
Hi,
Since https://issues.apache.org/jira/browse/WICKET-4014 (Wicket 1.5.1)
Wicket is able to handle automatically page expiration for mounted
pages. I.e. if the user clicks a link and the page is already expired
then depending on
org.apache.wicket.settings.IPageSettings#getRecreateMountedPagesAfte
Hi,
I noticed this evening that when a page is expired, if we make an Ajax
call from this page (autocomplete for example), the Ajax call returns
a 302 and then the entire page content (and not a valid XML Ajax
response) - I investigated it with Firebug as there's no error
anywhere.
Could it be re
