[hibernate-issues] [Hibernate-JIRA] Commented: (HV-264) Validation of List of primitives
[
http://opensource.atlassian.com/projects/hibernate/browse/HV-264?page=com...
]
Hardy Ferentschik commented on HV-264:
--------------------------------------
At the moment you can apply @Email only at single String. @Email is not a built-in
constraint of Bean Validation. It is Hibernate Validator specific annotation which is
ported from the hibernate-legacy (Validator 3.x) code base.
In Bean Validation you can add additional ConstraintValidator implementations for a given
constraints to support additional types. For example, at the moment @Email has only one
ConstraintValidator
public class EmailValidator implements ConstraintValidator<Email, String>
you would need a
public class EmailValidator implements ConstraintValidator<Email,
Collection<String>>
I make this issue a feature request.
For now you could implement your own version of this ConstraintValidator and add it the
list of existing validator implementations for @Email via the xml configuration. There is
a constraint-definition node defined in the mappings xsd for that.
Validation of List of primitives
--------------------------------
Key: HV-264
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-264
Project: Hibernate Validator
Issue Type: Bug
Components: engine
Affects Versions: 4.0.1
Environment: Linux
Reporter: Michenaud Laurent
Hi,
I have a list of String in my bean :
These strings are email and i want to validate them.
So, i did in my bean :
@NotEmpty
@Email
//@Valid <= uncommenting that line doesnot change anything.
List<String> emails ;
At execution, i've got the error :
Exception in thread "main" javax.validation.UnexpectedTypeException: No
validator could be found for type: java.util.List<java.lang.String>
at
org.hibernate.validator.engine.ConstraintTree.verifyResolveWasUnique(ConstraintTree.java:236)
at
org.hibernate.validator.engine.ConstraintTree.findMatchingValidatorClass(ConstraintTree.java:219)
at
org.hibernate.validator.engine.ConstraintTree.getInitializedValidator(ConstraintTree.java:167)
at
org.hibernate.validator.engine.ConstraintTree.validateConstraints(ConstraintTree.java:113)
at
org.hibernate.validator.metadata.MetaConstraint.validateConstraint(MetaConstraint.java:121)
at
org.hibernate.validator.engine.ValidatorImpl.validateConstraint(ValidatorImpl.java:334)
at
org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForRedefinedDefaultGroup(ValidatorImpl.java:278)
at
org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:260)
at
org.hibernate.validator.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:213)
at org.hibernate.validator.engine.ValidatorImpl.validate(ValidatorImpl.java:119)
at com.adeuza.movalys.validation.hibernate.TestMain.main(TestMain.java:75)
I don't know if it is a bug in hibernate validator. I have looked at the JSR303 and i
have not seen anything
about List of primitives. You can validate per example List<Person> with @Valid and
it works well because
the validator knows about Person class.
I have used a little the Oval framework and with it, you can tell if the check applies to
the container,
or the values inside, or the keys(for map). I don't know if you can do that with
JSR303.
I'm interesting with your point of view.
--
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