[
https://issues.apache.org/jira/browse/WICKET-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420131#comment-13420131
]
vineet semwal commented on WICKET-4594:
---------------------------------------
currently callback url parameters are not passed to new page instance (even in
case of stateless) in beta3 though i don't know how this (4594) change did it
before it used to in beta2 ..
however i believe pageparameters are ones which gets used up when page is
constructed ,extraparameters or any callback url parameters which are added to
callback url are different they are not meant to be passed as
pageparameters(even in case of stateless), they can be retrieved from request
parameters on the request in onEvent so say in the quickstart provided,the
value associated with key can be retrieved in onEvent by
requestcycle.getRequest().getRequestParameters().getParameterValue("ye") and
then value can be used for label.
i know this is not the way people currently do with stateless ajax but this
appears to me the most correct way.
> Do not use the parsed PageParameters when re-creating an expired page
> ---------------------------------------------------------------------
>
> Key: WICKET-4594
> URL: https://issues.apache.org/jira/browse/WICKET-4594
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.7
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 6.0.0-beta3, 1.5.8
>
> Attachments: WICKET-4594.patch.diff, example.tar.gz
>
>
> WICKET-4014 and WICKET-4290 provided functionality to re-create an expired
> page if there is a mount path in the current request's url.
> There is a minor problem with that because the page parameters are passed to
> the freshly created page. I.e. parameters for a callback behavior are now set
> as page construction parameters.
> Since the execution of the behavior is ignored for the recreated page these
> parameters should be ignored too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
