[
https://jira.jboss.org/jira/browse/RF-8172?page=com.atlassian.jira.plugin...
]
Alexander Smirnov resolved RF-8172.
-----------------------------------
Fix Version/s: 3.3.3.BETA1
Resolution: Done
Bean validator interface has been moved to richfaces-api;
org.richfaces.component.UIRichInput#validateValue method passes null values to validators
that implement such interface.
Components that extend UIRichInput or pass null values to bean validator:
pickList
inplaceInput
comboBox
inplaceSelect
calendar
Pass null values to BeanValidator from richfaces UIInput-based
components
-------------------------------------------------------------------------
Key: RF-8172
URL:
https://jira.jboss.org/jira/browse/RF-8172
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: component
Affects Versions: 3.3.2.SR1
Reporter: Alexander Smirnov
Assignee: Alexander Smirnov
Fix For: 3.3.3.BETA1
Initials: After we designed our validation tags we got some forum posts with questions
"why notNull/Empty validation not works for h:input's". We decided to fix
the problem by extending standard component classes and rewriting validateValue there. So
it started to works for standard components.
BUT - our inputs like comboBox, calendar(not checked others but think the problem will be
the same) extends stanadrd UIInput. So all of them has initial problem which we solved for
standard components. It's looks wery weird because customers will not even looks at
debug but just check that for example h:input works but rich:comboBox - not. And they
consider this as issue - not taking into consideration that standard inputs works only
because of our custom classes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira