[
https://issues.apache.org/jira/browse/WICKET-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619854#action_12619854
]
Johan Compagner commented on WICKET-1766:
-----------------------------------------
huh?
No the first call to isVisible() checks if we can call the onclick event on it
yes or now.
It can call it because the table says i am visible at this time.. (rowcount > 0)
Then in the onclick you remove it and then the table is rendered again..
But now the table is NOT rendered because the isVisible() will now return false
because you deleted the row in the onclick and rowcount == 0
Rowcount couldnt be cached because then we had a problem that the table says it
is visible and wants to render 1 row that isnt there.
> Method size() of a data provider is invoked twice.
> --------------------------------------------------
>
> Key: WICKET-1766
> URL: https://issues.apache.org/jira/browse/WICKET-1766
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.4
> Environment: Ubuntu
> Reporter: Rik van der Kleij
> Assignee: Igor Vaynberg
> Priority: Minor
>
> Method size() of a data provider is invoked twice during one request. This
> happens when navigating to a next or latest page in a data table. During
> debugging I noticed that the onDetach() of AbstractPageableView is invoked an
> extra time. Implementations of size() normally query the database so it will
> slow down the performance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
