[jira] Resolved: (WICKET-2025) isVisible should not be called after detach

["Juergen Donnerstag (JIRA)" <ji...@apache.org>]

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

Juergen Donnerstag resolved WICKET-2025.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4-RC2
         Assignee: Juergen Donnerstag

thanks

> isVisible should not be called after detach
> -------------------------------------------
>
>                 Key: WICKET-2025
>                 URL: https://issues.apache.org/jira/browse/WICKET-2025
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4-RC1
>            Reporter: Erik van Oosten
>            Assignee: Juergen Donnerstag
>             Fix For: 1.4-RC2
>
>
> I think isVisible should not be called after detach to prevent model reloads.
> I found one call to isVisible after detach in method ComponentRequestTarget#respond(RequestCycle). That method initiates a detach and then calls page.endComponentRender. This leads to a call to Page#checkRendering which calls isVisibleInHierarchy() and from there isVisible(). Method checkRendering only does something when the debug setting 'componentUseCheck' is enabled (which according to the javadoc is true by default). 
> Short term workaround: set debug setting 'componentUseCheck' to false.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.