Validation error: "No validator could be found for type: java.lang.Integer"

Question

I am working on a project with Spring why do I keep getting the following error?

javax.validation.UnexpectedTypeException:
No validator could be found for type: java.lang.Integer

Here is my code:

package com.s2rsolutions.model;

import java.util.Date;

import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.Id;
import javax.persistence.Table;
import javax.validation.constraints.Size;

import org.hibernate.validator.constraints.NotEmpty;

@Entity
@Table(name = "sales")
public class Sales {

    @NotEmpty(message = "The above field must not be blank.")
    @Column(name = "ttl_d_sls_lst_mth", nullable = false)
    private Integer ttl_d_sls_lst_mth;

    @NotEmpty(message = "The above field must not be blank.")
    @Column(name = "ttl_d_sls_6_mth", nullable = false)
    private Integer ttl_d_sls_6_mth;

    @Column(name = "date_added")
    private Date addedDate;

    @Id
    @Column(name = "username")
    private String username;

    // other fields/getters/setters omitted for brevity

}

Looks like this is similar to what I faced earlier, this post helped me. To customize the error messages from failing at the bind time. Look this link for more details on creating a MessageSource bean in your application context and create a messages.properties resource bundle : — Kris
– Kris, Commented May 12, 2011 at 19:02

Affe · Accepted Answer · 2011-05-12 19:08:34Z

238

As per the javadoc of NotEmpty, Integer is not a valid type for it to check. It's for Strings and collections. If you just want to make sure an Integer has some value, javax.validation.constraints.NotNull is all you need.

public @interface NotEmpty

Asserts that the annotated string, collection, map or array is not null or empty.

answered May 12, 2011 at 19:08

Affe

48.1k12 gold badges85 silver badges86 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

ChssPly76 Over a year ago

+1. @NotEmpty, being proprietary, should be avoided altogether. It can be replaced by @NotNull, @Range and @Size (depending on context)

Affe Over a year ago

Agree on avoiding vendor specific features when possible, but it is to its credit Free and Open Source :)

Michael Piefel Over a year ago

Amazing how easy it is to unintentionally annotate an integer field with a @NotEmpty annotation. And then you get the less than helpful warning “No validator could be found for constraint 'javax.validation.constraints.Size' validating type 'java.lang.Integer'.”

Beezer Over a year ago

What would be excellent is if there is a way of being able to get a more verbose error message to understand which property caused the issue for the exception thrown. If anyone knows this I would be very glad to know the answer. Thanks for the post it solved my problem.

Affe Over a year ago

@Beezer ConstraintViolationException has an additional method getConstraintViolations() that returns the list of ConstraintViolation objects that then each have a message.

N. berouain · Accepted Answer · 2020-01-25 16:05:01Z

14

As stated in problem, to solve this error you MUST use correct annotations. In above problem, @NotBlank or @NotEmpty annotation must be applied on any String field only.

To validate long type field, use annotation @NotNull.

edited Jan 25, 2020 at 16:05

N. berouain

1,33115 silver badges17 bronze badges

answered Jan 25, 2020 at 10:44

Thamaraikannan Rajendran

1371 silver badge2 bronze badges

1 Comment

Jose Anibal Rodriguez Over a year ago

@NotEmpty can also, be applied to List or any other collection.

Nitin Jha · Accepted Answer · 2018-12-07 09:44:36Z

12

As the question is asked simply use @Min(1) instead of @size on integer fields and it will work.

answered Dec 7, 2018 at 9:44

Nitin Jha

1,9432 gold badges14 silver badges14 bronze badges

Comments

Dr.jacky · Accepted Answer · 2020-01-02 10:34:21Z

6

For this type error: UnexpectedTypeException ERROR: We are trying to use incorrect Hibernate validator annotation on any bean property. For this same issue for my Springboot project( validating type 'java.lang.Integer')

The solution that worked for me is using @NotNull for Integer.

edited Jan 2, 2020 at 10:34

Dr.jacky

3,6036 gold badges58 silver badges98 bronze badges

answered Oct 25, 2019 at 19:05

tej

711 silver badge2 bronze badges

1 Comment

Nick Martin Over a year ago

Please improve formatting and explain why you are suggesting this as a suitable answer

spielbug · Accepted Answer · 2018-08-24 12:24:20Z

4

You can add hibernate validator dependency, to provide a Validator

<dependency>
    <groupId>org.hibernate</groupId>
    <artifactId>hibernate-validator</artifactId>
    <version>6.0.12.Final</version>
</dependency>

answered Aug 24, 2018 at 12:24

spielbug

1,40115 silver badges18 bronze badges

Collectives™ on Stack Overflow

Validation error: "No validator could be found for type: java.lang.Integer"

5 Answers 5

5 Comments

1 Comment

Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

5 Comments

1 Comment

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related