[
https://issues.jboss.org/browse/RFPL-1839?page=com.atlassian.jira.plugin....
]
Jiří Štefek resolved RFPL-1839.
-------------------------------
Resolution: Out of Date
This cannot be reproduced in latest 4.5.2+ Snapshots of Metamer. Tried with WildFly 8.2
and Tomcat 8 + Mojarra.
There were no tests for checking this behaviour, so I have Introduced a method to check
the order of elements before and after the submit and added it to a few tests.
Metamer: orderingList: updated sorting doesn't result into new
rodering in output. Need submit twice to update output
---------------------------------------------------------------------------------------------------------------------
Key: RFPL-1839
URL:
https://issues.jboss.org/browse/RFPL-1839
Project: RichFaces Planning
Issue Type: Bug
Components: QE
Affects Versions: 4.1.0.CR1
Environment: RichFaces 4.1.0.20111111-CR1
Metamer 4.1.0.20111111-CR1 r.22924
Mojarra 2.1.3-SNAPSHOT
Apache Tomcat 7.0.22
Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
Chrome 15.0.874.106 @ Linux i686, Firefox 8.0
Reporter: Ján Jamrich
Assignee: Jiří Štefek
Updated ordering in orderList doesn't results into appropriate output list ordering.
Need to submit form again, then get correct ordering in output.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)