Subclasses must implement the abstract {@link #resolveCode}method. For efficient resolution of messages without arguments, the {@link #resolveCodeWithoutArguments} method should be overriddenas well, resolving messages without a MessageFormat being involved.
Note: By default, message texts are only parsed through MessageFormat if arguments have been passed in for the message. In case of no arguments, message texts will be returned as-is. As a consequence, you should only use MessageFormat escaping for messages with actual arguments, and keep all other messages unescaped. If you prefer to escape all messages, set the "alwaysUseMessageFormat" flag to "true".
Supports not only MessageSourceResolvables as primary messages but also resolution of message arguments that are in turn MessageSourceResolvables themselves.
This class does not implement caching of messages per code, thus subclasses can dynamically change messages over time. Subclasses are encouraged to cache their messages in a modification-aware fashion, allowing for hot deployment of updated messages. @author Juergen Hoeller @author Rod Johnson @see #resolveCode(String,java.util.Locale) @see #resolveCodeWithoutArguments(String,java.util.Locale) @see #setAlwaysUseMessageFormat @see java.text.MessageFormat
|
|
|
|