[Hibernate-JIRA] Created: (BVAL-34) Expose a simple message for consumption by metadata tools like JSF client validation?
by Emmanuel Bernard (JIRA)
Expose a simple message for consumption by metadata tools like JSF client validation?
-------------------------------------------------------------------------------------
Key: BVAL-34
URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-34
Project: Bean Validation
Issue Type: New Feature
Components: spec-general
Reporter: Emmanuel Bernard
>From Pete
True client side validation (no ajax calls allowed). JSR303 will expose (extensible) metadata about the validations on properties. This metadata can be used to attach a client side validator. JSF should provide client side validators for all the JSR303 built in metadata, and provide a system to register other JSR303-metadata/client side validator pairs. Open issues include:
* What metadata JSR303 should expose to make this possible
* How to provide error messages, as these can't be generated when the validation error occurs. The proposal is to provide a basic client side message context which can be used to populate the error message (including substituting in the input label and submitted value). The developer would provide both a simple message (for the client side) and a more complex one for when the full message context is available on the server
* How to attach the correct client side validator to the html input tag.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[Hibernate-JIRA] Created: (BVAL-4) Return value for @NotEmpty for null values
by Hardy Ferentschik (JIRA)
Return value for @NotEmpty for null values
------------------------------------------
Key: BVAL-4
URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-4
Project: Bean Validation
Issue Type: Task
Components: spec-general
Reporter: Hardy Ferentschik
The spec says:
"While not mandatory, it is considered a good parctice to split the core constraint from the not null constraint validation ..."
As examples we have @Email and @Length, but would the same not apply for @NotEmpty. From a programmers point of view I think @NotEmpty should return true for null values. However, one could argue that from a GUI perspective it would not make sense to get to different validation messages. In fact, a user does not know what it means that the value cannot be null. However, any decent GUI/web framework will make sure that a string value will always be passed as empty string when nothing is entered by the user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months