cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Epheser (JIRA)" <>
Subject [jira] Updated: (COCOON-1877) [PATCH] Pageable Repeater
Date Fri, 28 Jul 2006 10:44:16 GMT
     [ ]

Matthias Epheser updated COCOON-1877:

    Attachment: repeater-pagination-2.patch

repeater-pagination-2.patch adds the storage area to the pagination binding. After a page-change,
updated rows are not dircetly saved to the JXPatchContext but to some internal cache objects.
The standard doSave() - code is not executed until the submit button is invoked.

> [PATCH] Pageable Repeater
> -------------------------
>                 Key: COCOON-1877
>                 URL:
>             Project: Cocoon
>          Issue Type: New Feature
>          Components: Blocks: Forms
>            Reporter: Matthias Epheser
>         Attachments: repeater-pagination-2.patch, repeater-pagination.patch
> This patch provides simple pagination for the repeater widget using the binding.
> It consists of 3 main parts: It extends the repeater-definition to configure the pages,
adds a ChangePageAction for userinteraction and modifies the binding so savePage/loadPage
can be performed after the action is called.
> Speaking of a first demo with basic functionality there are some known issues and missing
> - We plan to use some internal "storage area" inside the binding that contains the updated
rows after a page-change. The real doSave() code should be called just once after the form
was submitted. This should provide better integration to scenarios where persistence frameworks
like hibernate are used.
> - The userinterface needs to be extended to features like next/first/last-page buttons
and the common "first 1 2 3 4 5 next" group of links to choose pages directly.
> - Filtering and Sorting of the rows would be nice and could maybe accomplished extending
the storage area implementation.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message