Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.0.0.GA
-
Fix Version/s: 3.1.0.BETA1, 3.1
-
Component/s: Sample Apps
-
Labels:None
-
Environment:Showcase App Mojarra MyFaces
-
Assignee Priority:P2
-
Affects:Sample App./Tutorial
Description
While the issue can be replicated with our showcase example, it's not specific to ICEfaces and can be reproduced in a simple test case running either Mojarra or MyFaces
To reproduce:
- build showcase with Myfaces (ant clean servlet profile -Dmyfaces="true") or Mojarra
- deploy to Tomcat7.
- load the page in any browser: http://localhost:8080/showcase/showcase.jsf?exp=dataTableBean&grp=aceMenu
- choose the Pagination example
- select on the page: Table Rows (1-30) = 5 and tab out
- then change Selected Page (1-6) = 6 and submit.
- a validation message renders on the page: "Specified attribute is not between the expected values of 1 and 3."
The issue being that use of an EL expression for the maximum attribute doesn't work.
To reproduce:
- build showcase with Myfaces (ant clean servlet profile -Dmyfaces="true") or Mojarra
- deploy to Tomcat7.
- load the page in any browser: http://localhost:8080/showcase/showcase.jsf?exp=dataTableBean&grp=aceMenu
- choose the Pagination example
- select on the page: Table Rows (1-30) = 5 and tab out
- then change Selected Page (1-6) = 6 and submit.
- a validation message renders on the page: "Specified attribute is not between the expected values of 1 and 3."
The issue being that use of an EL expression for the maximum attribute doesn't work.
Nils said:
private int rows = 10;
{ return (int)Math.ceil(30.0/(double)rows); }... public int getStartPageMaximum()
so there should only be 3 pages by default. changing to 5 rows should cause statePageMaximum to return 6
and it does because the text says pages 1-6
however the validator isn't updated somehow
nothing to do with the table directly
looks like it could be myfaces issue with validators