[Myfaces Wiki] Update of "Extensions/Validator/JSR303/ClientSide" by jankeesvanandel

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Myfaces Wiki" for change notification.

The "Extensions/Validator/JSR303/ClientSide" page has been changed by jankeesvanandel.
http://wiki.apache.org/myfaces/Extensions/Validator/JSR303/ClientSide?action=diff&rev1=2&rev2=3

--------------------------------------------------

   * Adding js transparently based on
     * Constraints
     * JSF validators/validation methods
-    * JSF convertes (client-side conversion (ClientConverter))
+    * JSF converters (client-side conversion (ClientConverter))
   * Client side conversion(ClientConverter) is also required to be compatible with server side validation processing.
   * Group validation (partial validation)
   * Skipable validation (see @SkipValidation)
+    * Skip validation for immediate components
   * Bypass validation for command components
     (see @BypassValidation and @BypassBeanValidation (= existing ExtVal-add-ons))
   * Cross-validation
@@ -25, +26 @@

   * Interaction with Ajax-validation
     (e.g. for model aware validation)
   * Restrict exposing sensitive information to the client -> fallback to Ajax validation
+  * Input masking for dates, numbers, etc., based on the server side formats.
+  * Correctly positioning and styling error messages, so the user doesn't see the difference between client-side and server-side generated messages.
+    (we might need to do some tricks here, since UIMessage(s) doesn't render anything when there are no messages).
  
  == Reusing annotations ==
   * Any validation constraints
   * @ResourceDependency (@ResourceDependencies)
+  * Reuse existing BeanValidation annotations
+    (we probably need to disable Bean Validation, because otherwise the user may see double error messages)
  
  == Changing existing annotations ==
   - Additional target for @ResourceDependency (java.lang.annotation.ElementType.METHOD)
@@ -44, +50 @@

  == At the client ==
   * JavaScript
   * CSS (for highlighting - has to consider possible skinning approaches)
+  * Minimize JS code in web page (performance, external JS file may be cached, readability...)
  
  == At the server ==
   * JSF