[
https://issues.apache.org/jira/browse/WICKET-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872076#comment-13872076
]
Martin Grigorov commented on WICKET-5068:
-----------------------------------------
#canCallListenerInterfaceAfterExpiry() is named so to be close to the already
existing org.apache.wicket.Component#canCallListenerInterface(Method)
I don't mind to rename it to #getCallListenerInterfaceAfterExpiry(). I just
like the current one better. It doesn't follow the Java bean naming conventions
but sounds/reads better this way.
> PageParameters missing from re-created Page
> -------------------------------------------
>
> Key: WICKET-5068
> URL: https://issues.apache.org/jira/browse/WICKET-5068
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.4.0
> Environment: All
> Reporter: bernard
> Attachments: wicket-5068.patch
>
>
> WICKET-4594 removes existing PageParameters when re-creating an expired page.
> It does this under the assumption that the parameters are not needed for
> callback behavior that must not be executed after expiry.
> However PageParameters are needed even without execution of callback behavior.
> In trivial cases, a page cannot be re-constructed successfully without
> PageParameters e.g. a view page for a customer order needs the order ID from
> its PageParameters.
> There is a bit of an irony about this. To improve the recovery behavior, i.e.
> to avoid the dreaded PageExpiryException, one needs to create some client
> state which is then lost on re-creation after expiry.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
