]
Jan Papousek commented on RF-11264:
-----------------------------------
Same behaviour occurs in Metamer page
faces/components/richInputNumberSlider/jsr303.xhtml.
rich:select validation and ajax update doesn't work reliable
------------------------------------------------------------
Key: RF-11264
URL:
https://issues.jboss.org/browse/RF-11264
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-selects
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0.20110805-M1
r.10246d45dddd1d2aa2034317d5a832394cc919f9
Metamer 4.1.0.20110805-M1 r.22604
Apache MyFaces JSF-2.1 Core Impl 2.1.1
JBoss AS 6.0.0.Final
Java(TM) SE Runtime Environment 1.6.0_26-b03 @Linux
Chrome 12.0.742.112 @ Linux i686
Reporter: Ján Jamrich
Assignee: Jay Balunas
Labels: myfaces
Examples for rich:select in Metamer doesn't perform client side validation (or
display validation messages) reliable. Sometime for page with multiple rich:select inputs
validated to different rules are validation messages displayed, then refresh page and try
again, and the validation doesn't perform. The same with (correct) values entered into
validated inputs. If entered valid input, value is displayed in output element, but when
entered an incorrect value (even validation message didn't appear) value is no more
displayed in output.
Another problem is with simple page (faces/components/richSelect/fAjax.xhtml) with
rich:select, where submit by ajax behavior doesn't work. Item selected by mouse is
displayed in input as selected, but doesn't appear in output element.
Next problem is with submitting form containing various rich:select inputs with different
(bean - JSR303) validations - with submit by JSF and Ajax button. When submit with JSF
submit button, all validations are performed correctly. But when submit by Ajax submit
button, only one validation message is displayed (for last select), but in log are all
messages with warning that they are unhandled:
11:23:13,835 WARNING [org.apache.myfaces.lifecycle.RenderResponseExecutor] There are some
unhandled FacesMessages, this means not every FacesMessage had a chance to be rendered.
These unhandled FacesMessages are:
- form:input1: may not be empty
- form:input2: must match "[a-z].*"
- form:input3: size must be between 3 and 6
- string is not "RichFaces"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: