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 777931
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T19:41:11+00:00 2026-05-14T19:41:11+00:00

I’ve implemented a ReloadableResourceBundleMessageSource in my Spring MVC application which I use to display

  • 0

I’ve implemented a ReloadableResourceBundleMessageSource in my Spring MVC application which I use to display prettier error messages for binding exceptions. The problem I’m having is that, due to a company policy, these errors must be displayed in the following format:

[inputData] is not a valid [fieldName].

The field name is accessible by default in my message properties file (as the {0} argument), but I can’t figure out a way to display the invalid user input. Is this possible?

  • 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-05-14T19:41:11+00:00Added an answer on May 14, 2026 at 7:41 pm

    Yes,

    errors Tag does not allow you get the “value” supplied by your user – See link

    Suppose here goes your errors.properties (root of the classpath) file (Notice i am using just one {0} argument)

    // errors.properties
    
    error.invalid=is not a valid {0}
    

    When validating your command object, you do as follows

    import static org.springframework.validation.ValidationUtils.*;
    
    public boolean validate(Object command, Errors errors) {
    
        Person person = (Person) command;
    
        /**
          * new Object [] plays the role of the supplied arguments
          */
        rejectIfEmpty(errors, "age", "error.invalid", new Object[] {"Age"}, "Age is required");
    
        /**
          * If your label is a resource bundle key, use DefaultMessageSourceResolvable instead
          *
          * rejectIfEmpty(errors, "age", "error.invalid", new Object[] {new DefaultMessageSourceResolvable("person.age")}, "Age is required");
          */
    
    }
    

    UPDATE

    But to get your goal, you must provide a custom messageSource (Notice implements instead of extends)

    public class PolicyMessageSource implements MessageSource {
    
        private ResourceBundleMessageSource resourceBundle;
    
        public PolicyMessageSource() {
            resourceBundle = new ResourceBundleMessageSource();
    
            /**
              * Suppose your resource bundle is called messages.properties (root of the classpath)
              */
            resourceBundle.setBasenames(new String[] {"messages"});
        }
    
        public String getMessage(String code, Object[] args, String defaultMessage, Locale locale) {
            return resourceBundle.getMessage(code, args, defaultMessage, locale);
        }
    
        public String getMessage(String code, Object[] args, Locale locale) throws NoSuchMessageException {
            return resourceBundle.getMessage(code, args, locale);
        }
    
        public String getMessage(MessageSourceResolvable resolvable, Locale locale) throws NoSuchMessageException {
            if(resolvable instanceof FieldError) {
                FieldError fieldError = (FieldError) resolvable;
    
                /**
                  * Here goes what you want
                  */
                return fieldError.getRejectedValue() + resourceBundle.getMessage(resolvable, locale);
            }
    
            return resourceBundle.getMessage(resolvable, locale);
        }
    
    }
    

    So define your PolicyMessageSource as messageSource

    <bean id="messageSource" class="br.com.spring.PolicyMessageSource"/>
    

    Be aware you must define just one messageSource instance called messageSource. Notice i am using ResourceBundleMessageSource instead. You must check out the same approach when using ReloadableResourceBundleMessageSource. Keep this in mind.

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

Sidebar

Related Questions

No related questions found

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.