]
Brian Leathem commented on RF-12965:
------------------------------------
Pavol, can you prepare a framework test deomstrating this change? This will make it
easier to change the bundled mojarra version via command line options, and debug the test
in both scenarios looking for what caused the change.
Graph validator's behavior changed in Mojarra 2.1.18
----------------------------------------------------
Key: RF-12965
URL:
https://issues.jboss.org/browse/RF-12965
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: compatibility, component-validators
Affects Versions: 4.3.2
Environment: RichFaces 4.3.2-SNAPSHOT
Metamer 4.3.2-SNAPSHOT
works in Mojarra 2.1.17 and 2.1.7, broken in 2.1.18 to 2.1.21
Apache Tomcat 7.0.35
OpenJDK Runtime Environment 1.7.0_19-mockbuild_2013_04_19_20_08-b00 @ Linux
Chrome 26.0.1410.63 @ Linux x86_64, Firefox 20
Reporter: Pavol Pitonak
with Mojarra 2.1.17 and older:
# deploy Metamer to Tomcat and open
http://localhost:8080/metamer/faces/components/richGraphValidator/all.xhtml
# set groups attribute to "ValidationGroupBooleanInputs"
# uncheck "Select Boolean Checkbox"
# click "Apply changes", *result: message "may not be empty" next to
"Input Secret"*
# type ":-)" to input secret
# click "Apply changes", *result: message "Select Boolean Checkbox
isn't checked!" at the top of form*
# check the checkbox
# click "Apply changes", *result: message "Action successfully
done!"
with Mojarra 2.1.18 and newer:
# deploy Metamer to Tomcat and open
http://localhost:8080/metamer/faces/components/richGraphValidator/all.xhtml
# set groups attribute to "ValidationGroupBooleanInputs"
# uncheck "Select Boolean Checkbox"
# click "Apply changes", *result: message "Select Boolean Checkbox
isn't checked!" at the top of form*
# check the checkbox
# click "Apply changes", *result: message "Action successfully
done!"
# *input secret isn't validated at all, the same can be reproduced with calendar,
inplace input, input textarea, select many checkbox*
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: