I've reverted the commit for this issue. Since this issue doesn't seem
to affect many people I suggest to go ahead with the release and
postpone a possible extension of the API to untouch a page. In the
meantime to solve the problem of the issue we could suggest to use a
stateless page, which might use stateless AJAX components from WicketStuff.
Andrea.
Maybe we should expose an API to untouch a page?!
This will solve the case in WICKET-5933.
Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 7, 2015 at 10:56 AM, Emond Papegaaij <[email protected]
wrote:
I've reopened 5933, and I think the change should be reverted. The reason a
page is touched on retrieval is that there is no way to be sure the page
did
not change once it has been read from the page store. The user is free to
change the state of the page in whatever way he/she sees fit. Only a few of
those will mark the page dirty.
Best regards,
Emond
On Tuesday 07 July 2015 09:19:52 Sven Meier wrote:
