Pager wrong for large number of rows in a repeat

HCL Domino Domino Forum
1

  • This is likely related to the fact that an XPage apparently has to iterate over all the rows in a View in order to ascertain where the last page is, and it only does this up to a certain size. After that it just gives up, “for performance reasons”.- However that means if I should have 80 pages (at 50 rows per page), the last page on the Pager is simply and utterly wrong. I’m not using the default Pager, I’m using a custom one snagged from Dec’s XPages Tutorial, and it shows the last page as “9” instead of over 80. Each time I load a new (higher) page, this “last page” creeps ever upward.

  • The users are going to complain about that bitterly, management is going to like it even less, and neither are going to care the tiniest iota why it’s like that. Lotus needs to understand this seemingly innocuous issue is not innocuous at all. It’s end-user hostile, and it’s one more nail in the “not even close to ready for prime time” XPages saga.

  • Does Lotus seriously think people won’t employ large Views? (as if 4000 is “large”) My users, my manager, and therefore I could care less if the entire XPage system has to be scrapped and rewritten. The way it works now is utterly unacceptable for an enterprise grade application, and it must be fixed ASAP.

2

Subject: This is fixed in 8.5.2

There’s a property “ComputeLastPageAtAllCosts” or something like that. IBM decided that we developers need to make the decision about what constitutes a “performance problem.” golfclap :slight_smile:

Oh, and disclaimer: 8.5.2 is beta, it may not have the feature when it ships, etc. etc.

3

Subject: It better make it in…

  • Unless of course Lotus isn’t interested in enterprise level customers. Then who cares? There’s always Sharepoint.

  • It’s all well and good that Domino is LIGHT YEARS ahead of everyone in security and flexibility (and likely always will be), but if the XPages UI is garbage, it’s not relevant. The users and Luddite management only see the UI. Code slingers see all the other good stuff, but in all the places I’ve worked, code slingers don’t make purchase decisions.

  • If one has to go down to JSF to get it work, then what’s the point of using Domino? There are lots of perfectly good JSF containers already. XPages need to work, and work intuitively, out of the box. Period. Same goes for viewPanel, the poster child of useless “controls”.

Thanks for the info, Erik. I’ll keep my fingers crossed…