Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: 4.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 4.1
-
Assignee Priority:P1
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
Wraps the jQuery Validation min function in an ICEfaces / JSF friendly component.
---------------
Description: Requires the element to be the same as another one.
equalTo( other ) other Type: Selector
The selector for the element to compare the current values
Src: http://jqueryvalidation.org/equalTo-method
----------------
This validator should be supported by the following input components:
ACE
- ace:autoCompleteEntry
- ace:checkboxButton
- ace:checkboxButtons
- ace:comboBox
- ace:dateTimeEntry
- ace:maskedEntry
- ace:radioButton
- ace:radioButtons
- ace:richTextEntry
- ace:selectMenu
- ace:simpleSelectOneMenu
- ace:sliderEntry
- ace:textAreaEntry
- ace:textEntry
MOBI:
mobi:dateSpinner
mobi:timeSpinner
mobi:flipSwitch
Issue Links
- blocks
-
ICE-5377
Support for client-side validators for ACE and MOBI input components
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
As per ICE-5377 ace:sliderEntry and mobi:flipswitch will no longer be Validatetable.
Upon review we've decided that ace:sliderEntry should be supported, can be compared to another component with an integer value.
Also, mobi:flipSwitch, ace:checkboxButton, and ace:radioButton could be comparables for this validator.
Made slider validateable once again.
Made flipswitch component validateable as well.
Tested with ICEfaces 4 trunk r46213.
ace:sliderEntry and mobi:flipswitch using ace:clientValidateEqualTo are not functional. There are no messages rendered when the compared values differ.
Test applications at: /sliderEntryClientValidateEqualTo.jsf, /flipswitchClientValidateEqualTo.jsf
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/sliderEntry
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/flipswitch
Also as mentioned in ICE-5377, ace:radioButton, ace:checkboxButton, ace:comboBox, ace:selectMenu with ace:clientValidateEqualTo are also not functional. There are no messages rendered when the compared values differ.
Modified ace:radioButton and ace:checkboxButton renderers to satisfy jQuery validation constraints. Also fixed Validateable.getValidatedElementId method to point to the value holder element.
Modified ace:sliderEntry and mobi:flipswitch renderers to satisfy jQuery validation constraints.
The test cases for these components should be modified so that the compared components are placed in separate forms. When the referenced component value is changed a submit should be issued, only when the validated component is modified the submit should be blocked. This approach will ensure that the state on the client is kept in sync with the one on the server.
Due to the state complexities inherent with using this validator type we've decided it's real-world usefulness is limited in terms of being a client-side validator and will be removing it from the 4.1 release.
Backed off from implementing Validateable for ace:sliderEntry, mobi:flipswitch, ace:checkboxButton and ace:radioButton.
The actual EqualTo validator code needs to be removed from the repo as well.
Removed ace:clientValidateEqualto validator due inherent state synchronization complexities in the context of JSF.
Implemented ace:clientValidateEqualTo client-side validator. The validated component can compared only to other Validateable component. When defined, the label of the other component will be used in the validation message as reference.