Bug 871937 - RF-12474 : rich:select with enableManuelInput="true": Validation message is not displayed when the submitted value is not on the list.
Summary: RF-12474 : rich:select with enableManuelInput="true": Validation message is n...
Keywords:
Status: CLOSED DUPLICATE of bug 871870
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: RichFaces
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Brian Leathem
QA Contact: Pavol Pitonak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-31 18:35 UTC by ivassile
Modified: 2012-10-31 18:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-10-31 18:40:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ivassile 2012-10-31 18:35:50 UTC
Description of problem:
Per the RichFaces documentation:

"...If an invalid value is entered, it is highlighted as erroneous and validation messages appear with the submission..."

The validation message is not displayed when entering an invalid value (which is not on the list) and submitting it.

Test code:

<rich:select id="idSelect" value="#{backingBean.value}" enableManualInput="true">
    <f:selectItem itemLabel="Option 1" itemValue="Option 1" />
    <f:selectItem itemLabel="Option 2" itemValue="Option 2" />  		
</rich:select>



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Checkout https://github.com/papousek/richfaces-sanbox/tree/RF-12474, build it and deploy on JBoss AS 7
2. Open http://localhost:8080/richfaces-sandbox-jee6/
3. Select "a" item from the first rich:select and click on the first "send" button
4. Type "AAA" into the first rich:select and click on the first "send" button

Actual results:


Expected results:
Validation message should be present, but it isn't.

Additional info:
See https://issues.jboss.org/browse/RF-12474

Comment 1 ivassile 2012-10-31 18:40:11 UTC

*** This bug has been marked as a duplicate of bug 871870 ***


Note You need to log in before you can comment on or make changes to this bug.