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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T14:13:40+00:00 2026-05-15T14:13:40+00:00

It’s tedious and ugly to write things like: <input type=button value=<fmt:message key=submitKey /> />

  • 0

It’s tedious and ugly to write things like:

<input type="button" value="<fmt:message key="submitKey" />" />

And in case you want to nest the message tag in another tag’s attribute it becomes even worse.

Is there any shorthand for that. For example (like in JSF):

<h:commandButton value="#{msg.shareKey}" />

(spring-mvc-only solutions applicable)

  • 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-15T14:13:40+00:00Added an answer on May 15, 2026 at 2:13 pm

    This feels like a bit of a hack, but you could write a custom implementation of java.util.Map which, when get(key) is called, fetches the message from the Spring MessageSource. This Map could be added to the model under the msg key, allowing you to dereference the messages using ${msg.myKey}.

    Perhaps there’s some other dynamic structure than is recognised by JSP EL that isn’t a Map, but I can’t think of one offhand.

    public class I18nShorthandInterceptor extends HandlerInterceptorAdapter {
    
        private static final Logger logger = Logger.getLogger(I18nShorthandInterceptor.class);
    
        @Autowired
        private MessageSource messageSource;
    
        @Autowired
        private LocaleResolver localeResolver;
    
        @Override
        public boolean preHandle(HttpServletRequest request,
                HttpServletResponse response, Object handler) throws Exception {
    
            request.setAttribute("msg", new DelegationMap(localeResolver.resolveLocale(request)));
    
            return true;
        }
    
        private class DelegationMap extends AbstractMap<String, String> {
            private final Locale locale;
    
            public DelegationMap(Locale locale) {
                this.locale = locale;
            }
    
            @Override
            public String get(Object key) {
                try {
                    return messageSource.getMessage((String) key, null, locale);
                } catch (NoSuchMessageException ex) {
                    logger.warn(ex.getMessage());
                    return (String) key;
                }
            }
            @Override
            public Set<Map.Entry<String, String>> entrySet() {
                // no need to implement this
                return null;
            }
    
        }
    }
    

    As an alternative:

    <fmt:message key="key.name" var="var" />
    

    Then use ${var} as a regular EL.

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

Sidebar

Ask A Question

Stats

  • Questions 489k
  • Answers 489k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer Set selected="selected" for the option you want to be the… May 16, 2026 at 8:54 am
  • Editorial Team
    Editorial Team added an answer First of all, it's redundant to run the match twice… May 16, 2026 at 8:54 am
  • Editorial Team
    Editorial Team added an answer OK, so I'm answering my question just after I've asked… May 16, 2026 at 8:54 am

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

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.