Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.1
-
Component/s: ACE-Components, MOBI-Components
-
Labels:None
-
Environment:ICEfaces 4, ACE and MOBI input components.
-
Assignee Priority:P1
-
Support Case References:Support Case #12790 - https://icesoft.my.salesforce.com/5007000000c0y8f
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
This would entail implementing common JSF2 validators in JavaScript such that validation could occur in the browser without the need for a JSF lifecycle/roundtrip to occur. Certain static validation types could be supported this way. The relationship between the client-side mode and the normal JSF behavior would need to be carefully considered.
Issue Links
- depends on
-
ICE-10819 New ace:clientValidateLength client-side validator
-
- Closed
-
-
ICE-10820 New ace:clientValidatePattern client-side validator
-
- Closed
-
-
ICE-10822 New ace:clientValidateRequired client-side validator
-
- Closed
-
-
ICE-10823 New ace:clientValidateDecimal client-side validator
-
- Closed
-
-
ICE-10824 New ace:clientValidateValueRange client-side validator
-
- Closed
-
-
ICE-10827 New ace:clientValidateEqualTo client-side validator
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This would be a great feature! But with JSF 2 we aren't using JSF validators anymore but only the more generic JSR 303 validators. It should also be possible to easily implement client-side equivalents for custom JSR 303 validators.
RichFaces also has this feature:
http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=clientValidation&sample=jsr303&skin=blueSky
Lack of support for using client validators with ace:ajax and "immediate=true" is captured in
ICE-10897as a future improvement.Marking Resolved.