[
https://issues.apache.org/jira/browse/WICKET-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133648#comment-14133648
]
Martin Grigorov commented on WICKET-5693:
-----------------------------------------
No!
1. JIRA is not support forum!
If you have questions then you should ask here (at users@ mailing list).
If you have ideas then you should discuss them at dev@ mailing list.
2. If you want to not have the ?pageId in the url then you should stick to
stateless components and behaviors.
This is by design!
Stateful pages cannot work without the pageId parameter!
Solutions like NoVersionRequestMapper are pure hacks. Use them at your own
responsibility! Wicket developers are not responsible for them!
3. Wicket provides some default implementations for IRequestMapper interface.
But it also allows you to provide your own when you believe the default ones
are not optimal for you.
3.1. Wicket does its best to be backward compatible with previous versions.
Before every release we test the suggested new release with as much
applications as we have. If we find a regression we cancel the release and cut
a new one. You are very welcome to join us with testing your application, with
your custom implementations of Wicket interfaces, and report regressions !
> 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)
