You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Emond Papegaaij (Commented) (JIRA)" <ji...@apache.org> on 2011/11/25 10:48:43 UTC
[jira] [Commented] (WICKET-1175) IDataProvider-Overflow with size()
[ https://issues.apache.org/jira/browse/WICKET-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157060#comment-13157060 ]
Emond Papegaaij commented on WICKET-1175:
-----------------------------------------
The attached patch changes Loop back to int. Loop with a long does not work (you cannot add that many components to the parent). It also isn't needed for other components to function properly and it makes ListItem's constructors inconsistent.
> IDataProvider-Overflow with size()
> ----------------------------------
>
> Key: WICKET-1175
> URL: https://issues.apache.org/jira/browse/WICKET-1175
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.0-rc1
> Environment: any
> Reporter: Jan Kriesten
> Assignee: Igor Vaynberg
> Fix For: 6.0.0
>
> Attachments: 0001-Loop-should-not-use-long.patch
>
>
> Hi,
> I get an Integer-overflow with my Dataprovider (yeah, there are a couple of entries in the database). Is there a reason why size() and iterator( first, count ) are limited to Integer?
> Regards, --- Jan.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira