You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2009/08/13 17:34:15 UTC

[jira] Updated: (WICKET-2020) Callback after detaching the page but before the PageMap lock is released

     [ https://issues.apache.org/jira/browse/WICKET-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Dashorst updated WICKET-2020:
-------------------------------------

    Fix Version/s: 1.4.1
                   1.3.8

Was further implemented in 1.4.1 and 1.3.8

> 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: Igor Vaynberg
>             Fix For: 1.3.8, 1.4-RC2, 1.4.1
>
>
> 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.