Martin Grigorov píše v Út 18. 09. 2012 v 10:02 +0300:
Hi,
See https://issues.apache.org/jira/browse/WICKET-4594
The problem is that Wicket cannot differentiate between page
parameters and ajax request parameters
Maybe Wicket could off-load some of the AJAX params to headers?
Hi,
See https://issues.apache.org/jira/browse/WICKET-4594
The problem is that Wicket cannot differentiate between page
parameters and ajax request parameters and in case of page re-creation
all of them were used as page parameters for the new page instance.
When a page is automatically re-created
Hi,
Usage of Wicket's Ajax behaviors make the page stateful, so there is
no easy way to make it stateless.
The easiest solution is to use
org.apache.wicket.settings.IPageSettings#setRecreateMountedPagesAfterExpiry(false).
This way you'll see the configured
Ok, thanks. I set
this.getPageSettings().setRecreateMountedPagesAfterExpiry(false); in the
app class.
But, to my previous point:
The page is mounted and reached with all the necessary data (to get the
entity).
But on AjaxEditableLabel interaction, the page is created with empty
PageParameters.
On Mon, Sep 17, 2012 at 5:59 PM, Ondrej Zizka ozi...@redhat.com wrote:
Ok, thanks. I set
this.getPageSettings().setRecreateMountedPagesAfterExpiry(false); in the
app class.
But, to my previous point:
The page is mounted and reached with all the necessary data (to get the
entity).
But on
Is there a mechanism to let the page be re-created with the original
PageParameters?
Maybe they could be kept within JS of the page and sent with the AJAX
request? That would probably need a change in Wicket's AJAX code.
(Wicket 1.5)
That was the case until recently but there was
Hi,
I use a AjaxEditableLabel with a PropertyModel which points to an object
of the Page.
But after the session expires, clicking on the label to edit it causes
exception because the object of the page is empty (in my case, it
results into HBN's NoResultException).
What's the way to handle this?
