Bug 805105 - Pager for reservations doesn't work properly in sporsclub example
Summary: Pager for reservations doesn't work properly in sporsclub example
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Spring, Examples
Version: 2.0.0.ER3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.0.0.ER4
Assignee: Marius Bogoevici
QA Contact: Tomas Repel
URL:
Whiteboard: sportsclub
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 14:55 UTC by Tomas Repel
Modified: 2013-03-04 01:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-22 11:10:51 UTC
Type: ---


Attachments (Terms of Use)

Description Tomas Repel 2012-03-20 14:55:33 UTC
Description of problem:

If there are six reservations and user deletes one, then creates one, the pager still behaves as if there were only five reservations.

Version-Release number of selected component (if applicable):

WFK2 Beta1
Sportsclub, all variants, both hibernate and jpa ears
EAP6 Beta

How reproducible:

Always.

Steps to Reproduce:
1. build and deploy sportsclub example
2. go to Sports Club Reservations
3. click on Search button
4. click on page two
5. only one reservation should appear, delete it
6. click on Create button
7. create and save reservation
8. click on Search button
  
Actual results:

The pager is disabled.

Expected results:

There should be clickable button for page two where the newly added reservation should be displayed.

Additional info:

I think 'resetCurrentCount' and 'getRowCount' methods of AbstractExtendedDataModelHelper' should be called somewhere inside ReservationSearch class, so the pager will work with the proper value.

Comment 3 Tomas Repel 2012-04-19 14:52:57 UTC
Verified in WFK2 ER4

Comment 4 Karel Piwko 2012-06-22 11:10:51 UTC
These example related issues are fixed in WFK 2.0.0. Documenting them as fixed issues is not required.


Note You need to log in before you can comment on or make changes to this bug.