Re: Incorrect rowindex for datatable with tomahawk's sorting and scrolling features.

[gramani]

Mathias Brökelmann <[EMAIL PROTECTED]> wrote on 10/31/2005 08:35:43 AM:

> the problem is a little bit tricky ;)
>
> If you use preserveDataModel="true" the value of your datamodel is not
> requested until in the renderphase and will not be used for iteration
> and setting rowindex. This is the reason why you don´t get a valid
> value for your rowindex and rowdata in process application phase. I
> suggest you to change your jsp/bean code into one of the following
> way:
>
> - implement your action method into a WfAssignment wrapper class and
> use instances of it in your datamodel. Change your jsp code to call
> this action method in the wrapped class.
>
> - don´t use preserveDataModel and make sure that your getter method of
> the datamodel returns a non null or empty value during the decode
> phase.
>
> - provide a setter method for your datamodel. This method is being
> called in the update model phase to set the preserved datamodel. The
> preserved datamodel will only contain the values for the rendered
> page.
>

Thanks very much for your response. I shall try each of your ideas in turn. But I do have another question. You say using preserveDataModel="true" means that the value of the datamodel is not requested till the render phase. Does this explain why the rowIndex *always* is one less than the index of the largest index of the item currently shown? (I mean all pages have 5 items shown, and page1 has rowindex of all items as 4, page 2 has rowindex of all items as 9, page 3 has rowindex of all items as 14.. I can accept I think that rowindex can have wrong values but seems wierd that the the wrong values are following a pattern, and worse, always returning a constant (per page). Of course I am quite new with all this so I am probably missing something quite basic..

Thank you for your continued interest and time - I really appreciate it!
Geeta