Am I right in thinking that the PagerIterator is standalone, and does
not use the logic:interator (or the JSPTL forEach equivalent)?
Would these be added to the logic taglib, or a separate pager tablib?
Would the pager tablib be a good fit at Jakarta Taglibs?
Is it too "Model 2" for that, or could the pager also be created using
Model 1 techiques?
I've been talking to Morgan, and was about to submit the RowSet tags
there, as part of dbTags.
So, do we want to think about making this part of dbTags too (since
that's where the data would usually come from).
Should we suggest a second library for "detached" database tags? Maybe
dbTags2, as in Model2, with the RowSet and Pager tags.
We probably want to also start thinking about how JSPTL is going to
affect our taglibs, and what tags of ours might be moved to Jakarta
Taglibs. (Meaning a few of us should be committers there too ;-)
Oleg V Alexeev wrote:
>
> Hello struts-dev,
>
> I propose to add four classes to the framework -
> Pager - to store data about paging
> PagerIterator - to iterate via links
> PagerEntry - to represent link to the page
> PagerTag - to use Pager in jsp pages.
>
> There are two scenarios of Pager using -
> 1. create Pager in Action, store it in request and use early stored
> Pager object with PagerTag or standalone.
> 2. set all needed parameters as attributes of PageContext and pass
> its to the PagerTag
>
> Pager take 3 parameters -
> 1. pageSize
> 2. offset
> 3. totalSize
> and allow to get iterator (PagerIterator) via secuence of links
> (PagerEntry) to the pages.
> --
> Best regards,
> Oleg mailto:[EMAIL PROTECTED]
