Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8478443
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 10, 20262026-06-10T18:44:52+00:00 2026-06-10T18:44:52+00:00

I use Spring MVC together with Thymeleaf. I have an issue with Thymeleaf fields.hasErrors

  • 0

I use Spring MVC together with Thymeleaf. I have an issue with Thymeleaf fields.hasErrors which is as follows:

When a Bean Validation constraint error is raised (such as a @NotNull constraint), the following use of fields.hasErrors works perfectly:

<span class="help-inline" th:if="${#fields.hasErrors('member.email')}" th:text="#{message_form.validation.email}"></span>

An error message is displayed OK next to the email field.

However, when an “application-specific” error (as opposed to Bean Validation constraint error) is raised by my code (see code from controller below),

// FROM SPRING MVC CONTROLLER
if (!registrationService.isEmailAvailable(registrationInfo.getMember().getEmail())) {
    bindingResult.addError(new ObjectError("member.email", "email already used")); // TODO i18n
}

The th:if="${#fields.hasErrors('member.email')}" does not evaluate to true and no error message is displayed….

The only way I have found to display those “application-specific” errors is to include the following underneath the form:

<div id="errors" class="alert alert-error">
    <ul th:if="${#fields.hasErrors('*')}">
        <li th:each="err : ${#fields.errors('*')}" th:text="${err}"></li>
    </ul>
</div>

Then, it will display “email already used” as a list item.

Can anyone please clarify the behavior of th:if="${#fields.hasErrors('member.email')}" and especially tell me why it will evaluate to false in the case of “application specific” errors?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-10T18:44:54+00:00Added an answer on June 10, 2026 at 6:44 pm

    I found the solution to my isue: My problem comes from an incorrect usage of the Spring API.

    I should be using a FieldError instead of an ObjectError.

    So changing from:

       //FROM SPRING MVC CONTROLLER
        if (!registrationService.isEmailAvailable(registrationInfo.getMember().getEmail())) {
            bindingResult.addError(new ObjectError("member.email", "email already used"));//TODO i18n
        }
    

    to

       //FROM SPRING MVC CONTROLLER
        if (!registrationService.isEmailAvailable(registrationInfo.getMember().getEmail())) {
            bindingResult.addError(new FieldError("registrationInfo","member.email", "email already used"));//TODO i18n
        }
    

    solved the problem.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I use Spring MVC together with Spring Roo and I have added a JPA
I use JSR303 bean validation annotations in my spring-mvc managed bean to validate text
I use Spring MVC 3.0 and JSP. I have an object: public class ObjectWrapper
I have learned how to use Spring MVC 3, but I am very interested
I am trying to use Spring AOP with Spring MVC Controller. I have 3
I have a REST web service using spring MVC which is external-facing. I would
I use Spring MVC with java config. And I have two context configuration classes:
I use Spring Roo + Jpa + Spring MVC. I have several @ManyToOne and
I am working under a web application which use spring mvc + mybatis +
With spring MVC, do you have to use one of the special form controllers

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.