[
https://issues.apache.org/jira/browse/WICKET-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juergen Donnerstag resolved WICKET-2020.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC2
Assignee: Juergen Donnerstag
I changed to the javadoc to explain that detach() should not be called by any
user, but that subclassing is allowed.
> Callback after detaching the page but before the PageMap lock is released
> -------------------------------------------------------------------------
>
> Key: WICKET-2020
> URL: https://issues.apache.org/jira/browse/WICKET-2020
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.5
> Reporter: Emond Papegaaij
> Assignee: Juergen Donnerstag
> Fix For: 1.4-RC2
>
>
> Currently, it is not possible to perform any checks on a page after the
> request has been detached. In onEndRequest, the PageMap lock has already been
> cleared, making it unsafe to access the pages involved in the request. Would
> it be possible to add an extra callback method (ie. onAfterTargetDetach()) to
> RequestCycle directly after detaching the request targets? We need such a
> callback to check (in development mode) if all models are detached correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
