validator.getPotentialInvalidValues("user.username"

anicegirl911 · **Joined:** Tue Jul 03, 2007 11:36 am **Posts:** 24

How to easily validate the username below. I got the annotated vo. But it is in the jsf loginBean. How to validate the user.username property only.

clazz = Class.forName(com.abc.LoginBean);

ClassValidator validator = new ClassValidator(clazz);

InvalidValue[] validationMessages = validator.getPotentialInvalidValues("user.username", value);

emmanuel · **Posted:** Tue Jul 17, 2007 3:19 pm

Seems to be alright

anicegirl911 · **Joined:** Tue Jul 03, 2007 11:36 am **Posts:** 24

I have tried. It did not work. No error and validation also.

emmanuel · **Posted:** Wed Jul 18, 2007 1:27 pm

Check http://www.hibernate.org/hib_docs/validator/reference/en/html_single/#d0e436 and the unit test site. They contain working example.
Without more details, there is no way to tell what's wrong.

anicegirl911 · **Joined:** Tue Jul 03, 2007 11:36 am **Posts:** 24

Here is my code.

Code:

public class LoginBean {
   private User user;
。。。。。。
}

public class User {
    @org.hibernate.validator.Email
     private String email;
。。。
}

   Class   clazz = Class.forName("com.abc.LoginBean");   
   ClassValidator validator = new ClassValidator(clazz);
      
   InvalidValue[] validationMessages = validator.getPotentialInvalidValues("user.email", "wrongemail");

Is it because of @valid? It just mentioned for collection in the documentation, how about it is one to one relationship like Loginbean to User?

I have checked the seam validation tag source code. It does not use user.email as the parameter for ...invalidvalues(). It only use email as property name and create the validator for User class.

emmanuel · **Posted:** Thu Jul 19, 2007 9:35 am

Yes you need to add @Valid. Are you sure the ref doc mention only @Valid for collections? If true, please open a JIRA issue, this needs to be improved.

anicegirl911 · **Joined:** Tue Jul 03, 2007 11:36 am **Posts:** 24

Quote:

perform validation recursively
on the associated
object. If the object
is a Collection or an array,
the elements are validated
recursively. If the
object is a Map, the value
elements are validated recursively.

This is inside the document. For my understanding, the @valid is for the addressValidator.getInvalidValues(address); to tell hibernate whether want to validate the associated object. Since my code is explicitly tell hibernate to validate the property of associated object. So, it should not use @valid right?

I have tried @valid for user object. Did not work also.
What should i do now????

emmanuel · **Posted:** Wed Jul 25, 2007 1:27 pm

yes you should I guess, because a @Valid property could also be @NotNull or @Size for example

anicegirl911 · **Joined:** Tue Jul 03, 2007 11:36 am **Posts:** 24

I do not understand. I have tested with @valid with my example.

emmanuel · **Posted:** Thu Jul 26, 2007 1:46 pm

We don't understand each other it seems. Write a minimal but complete reproducible test case that shows what you expect and what you think is wrong and post it here. That will help