[
https://issues.apache.org/jira/browse/WICKET-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259991#comment-14259991
]
Hendy Irawan commented on WICKET-5693:
--------------------------------------
I too am confused with the behavior of {{setVersioned(false)}}
"True to turn on versioning for this component, false to turn it off for this
component and any children."
I see no effect on setting (on a stateful page, of course) this to false at all.
What's the intended behavior, so I can confirm that {{setVersioned(false)}} is
indeed working as the contract (i.e. Javadoc) suggested? I can't be sure, but
if {{setVersioned()}} is not working at all, then it should be both deprecated
and Javadoc corrected such that "this has no effect, stateful components are
always versioned".
> setVersioned(false) should force single Page Version
> ----------------------------------------------------
>
> Key: WICKET-5693
> URL: https://issues.apache.org/jira/browse/WICKET-5693
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.16.0
> Environment: All
> Reporter: Bernard
>
> After a form submit, we want the browser's back button to show the page
> before the form not the form page. That is a business requirement to prevent
> double submits.
> A web application can, via the use of Post-Redirect-Get, respond with the
> same URL as the form page's request URL, and let the browser history replace
> the form page with the form submit result page.
> In Wicket, we can attempt to achieve this behaviour by using the same page
> class for form and response - replacing a form panel with a response panel.
> Still Wicket creates multiple versions of the page which show as version
> numbers in the URL. To fix this, we call setVersioned(false).
> But still, the page is served with different URLs. This needs to be fixed in
> some way.
> We need full core framework support for this, without having to code
> workarounds. We have coded workarounds in the past, but these were broken by
> subsequent Wicket releases, even minor releases.
> We might need the URL to be version-free because the page's initial URL,
> being bookmarkable, would not have a version number. The only limitation
> should be the case where the browser does not have a cookie for the site,
> where the first page visited is the form page, having jsessionid in the URL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
