[
https://issues.apache.org/jira/browse/WICKET-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-1210.
-----------------------------------
Resolution: Invalid
ok, how about this:
datatable.visitchildren(new component.ivisitor() { visitcomponent(component c)
{ c.detach(); return continue_traversal; }});
reopen if it doesnt work
> Proposal to remove 'final' modifier for
> PagingNavigationIncrementLink.getPageNumber()
> -------------------------------------------------------------------------------------
>
> Key: WICKET-1210
> URL: https://issues.apache.org/jira/browse/WICKET-1210
> Project: Wicket
> Issue Type: Wish
> Components: wicket
> Affects Versions: 1.3.0-rc1
> Reporter: Thomas Jaeckle
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.3.0-rc3
>
>
> I wish to add a special behaviour to
> "PagingNavigationIncrementLink.getPageNumber()", which is final:
> http://www.nabble.com/PagingNavigationIncrementLink-special-behaviour-tf4935583.html
> Short: I extended "PagingNavigationIncrementLink.onClick()" so that more data
> is loaded from a service. After that I still want that the Page is changed,
> so I call "pageable.setCurrentPage(getPageNumber());".
> The "return Math.max(0, Math.min(pageable.getPageCount() - 1, idx));" breaks
> my neck because "pageable.getPageCount()" is missing the new added Page.
> It would be very helpful if PagingNavigationIncrementLink.getPageNumber()
> would not be final.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
