Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0
-
Fix Version/s: 1.1
-
Component/s: Paging/Sorting
-
Labels:None
-
Application server:TOMCAT5.0.18
Description
After deleting one record from the table, I want a user to be directed back to the current page of records spaning multiple pages.
To do this, I direct the user to the same url after deleting that record in Struts action.
This works fine as long as the record to be deleted is not the only record of the last page of multiple pages.
For example, 41 records are displayed in 3 pages (20 per page). The url for the last page with only one record is as follow:
http://fibldnw/test/paydispatch.do?action=payverify&d-16486-p=3
After deleting the last record, there are only two pages of records left. The above url will not display correctly. Changing the value of d-16486-p to any number greater than 3 will direct to the first page correctly however.
This actually applies to any situation where the last page is fully loaded and the value of page parameter in the request is the total page number plus 1.
To do this, I direct the user to the same url after deleting that record in Struts action.
This works fine as long as the record to be deleted is not the only record of the last page of multiple pages.
For example, 41 records are displayed in 3 pages (20 per page). The url for the last page with only one record is as follow:
http://fibldnw/test/paydispatch.do?action=payverify&d-16486-p=3
After deleting the last record, there are only two pages of records left. The above url will not display correctly. Changing the value of d-16486-p to any number greater than 3 will direct to the first page correctly however.
This actually applies to any situation where the last page is fully loaded and the value of page parameter in the request is the total page number plus 1.