UIData and large data. Change int to long

[glassfishrobot]

From https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=39

UIData use int data type. There is very long lists of items. F.g. very big
database table with billions or records. Of course, for such kind of data I
should use special datamodel which can get just shown items from DB. But all
methods of UIData return int values. Even getRowCount() can't return value
larger than int.

Environment

Operating System: All
Platform: All

Affected Versions

[1.1]

[glassfishrobot]

Reported by @edburns

[glassfishrobot]

Was assigned to rogerk

[glassfishrobot]

@edburns said:
Changing this would break binary backwards compatability for those that
subclassed UIData.

Have to ask the EG about it.

[glassfishrobot]

@edburns said:
Move to P4

[glassfishrobot]

@edburns said:
reassign to rogerk for parity of work.

[glassfishrobot]

rogerk said:
Based on EG feedback, I am closing this issue (at least for 1.2).
What Adam suggests sounds like the right approach.

Thanks, Roger.

Adam Winer wrote:

Erm, regarding UIData, why do we care about longs?

For a scroller component, yes, but it's not as if
anyone is going to actually show greater than 232
rows of data at any one time. You could use a UIData
to show windows of data into a "long" dataset; you'd
just have to be more careful with the model and the
scroller.

BTW, we'd also have to change DataModel, or introduce
a LongDataModel.

– Adam

Jacob Hookom wrote:

The javax.sql.RowSet uses an int for a row and so does
java.sql.ResultSet-- a long? wow.

[glassfishrobot]

@edburns said:
Prepare to delete "spec" subcomponent.

[glassfishrobot]

@edburns said:
Move all to 1.2

[glassfishrobot]

Marked as won't fix on Thursday, March 4th 2010, 6:09:28 am

[glassfishrobot]

luisalves00 said:
add:

abstract long getRowCount();
abstract long getRowIndex(); //this can be an issue because Collection.size() returns int..so only can be used on lazy loading

to

javax.faces.model.DataModel

this way lazy loading for huge Data Set is allowed and backwards compatibility is mantained

[glassfishrobot]

@manfredriem said:
Closing resolved issue out

[glassfishrobot]

This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-28