Hi,

I am moving from springmodules validation to hibernate-validation with annotation.

All has gone smoothly apart from the administration input user-password field.

I am using @size(min=4,max=8).

The validation is failing on the max=8.

I think this is because I am also using 'spring security' to encode the password in the database.

So my question is what is the way forward here - can I restrict the validation to just the user input or is there a better way ?

Thanks for any help.

If the plain-text password is not stored in the domain model then obviously you cannot validate plain-text by annotating the domain model.

You could store the plain-text password temporarily in an @Transient field. Use @NotNull on the encrypted field and @Size on the transient plain-text field. Or annotate the UI model and do additional validation before encryption.

Thanks I will give this a go

I have had a go at this and got it to work but very slightly differently.

I have:

@Transient
@Size(min=4,max=8)
private String validationPassword;

and

private String password;

As you implied you cannot have @NotNull here on a @Transient field.

However I could not put @NotNull on the persisted / encoded 'password' field as it would fail initial validation.

Thanks

Use groups. For example:



then



and



You can have @NotNull with @Transient as long as you control WHEN the field is validated (with groups). The transient field will be reset to null the next time you find the object from the database.

Thanks I had come across groups but I am using Spring MVC and from what I found I was not convinced I could get Spring to work with groups but I will check again.