[
https://issues.apache.org/jira/browse/WICKET-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pedro Santos updated WICKET-6316:
---------------------------------
Description:
A stateless link URL is encoded with the page id even in a stateless page by
default.
Stateless link URL in a stateful page mapped by Wicket's default mapper:
wicket/page?0-1.-statelessLink
and the same link encoded by AbstractBookmarkableMapper:
segment?-1.-statelessLink
It causes an inconsistent behavior where the the stateless link will be execute
on a fresh page or not based on how the page got mapped.
was:
A stateless link URL is encoded with the page id even in a stateless page by
default.
Stateless link URL in a stateful page mapped by Wicket's default mapper:
wicket/page?0-1.-statelessLink
and the same link encoded by AbstractBookmarkableMapper:
segment?-1.-statelessLink
This bug was also the cause of WICKET-6288, but in that case the stateless link
worked fine because it wasn't depending on the page's fresh state.
> Stateless link does not execute in a fresh page if its URL got encoded by
> Wicket's default request mapper
> ---------------------------------------------------------------------------------------------------------
>
> Key: WICKET-6316
> URL: https://issues.apache.org/jira/browse/WICKET-6316
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 7.6.0, 8.0.0-M3, 6.26.0
> Reporter: Pedro Santos
> Assignee: Pedro Santos
>
> A stateless link URL is encoded with the page id even in a stateless page by
> default.
> Stateless link URL in a stateful page mapped by Wicket's default mapper:
> wicket/page?0-1.-statelessLink
> and the same link encoded by AbstractBookmarkableMapper:
> segment?-1.-statelessLink
> It causes an inconsistent behavior where the the stateless link will be
> execute on a fresh page or not based on how the page got mapped.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
