java.lang.Objectorg.springframework.context.support.AbstractMessageSource
org.springframework.context.support.ResourceBundleMessageSource
All Implemented Interfaces:
BeanClassLoaderAware, HierarchicalMessageSource
This MessageSource caches both the accessed ResourceBundle instances and
the generated MessageFormats for each message. It also implements rendering of
no-arg messages without MessageFormat, as supported by the AbstractMessageSource
base class. The caching provided by this MessageSource is significantly faster
than the built-in caching of the java.util.ResourceBundle class.
Unfortunately, java.util.ResourceBundle caches loaded bundles
forever: Reloading a bundle during VM execution is not possible.
As this MessageSource relies on ResourceBundle, it faces the same limitation.
Consider ReloadableResourceBundleMessageSource for an alternative
that is capable of refreshing the underlying bundle files.
Rod - JohnsonJuergen - Hoeller| Fields inherited from org.springframework.context.support.AbstractMessageSource: |
|---|
| logger |
| Method from org.springframework.context.support.ResourceBundleMessageSource Summary: |
|---|
| doGetBundle, getBundleClassLoader, getMessageFormat, getResourceBundle, resolveCode, resolveCodeWithoutArguments, setBasename, setBasenames, setBeanClassLoader, setBundleClassLoader, toString |
| Methods from org.springframework.context.support.AbstractMessageSource: |
|---|
| createMessageFormat, formatMessage, getDefaultMessage, getMessage, getMessage, getMessage, getMessageFromParent, getMessageInternal, getParentMessageSource, isAlwaysUseMessageFormat, isUseCodeAsDefaultMessage, renderDefaultMessage, resolveArguments, resolveCode, resolveCodeWithoutArguments, setAlwaysUseMessageFormat, setParentMessageSource, setUseCodeAsDefaultMessage |
| Methods from java.lang.Object: |
|---|
| equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Method from org.springframework.context.support.ResourceBundleMessageSource Detail: |
|---|
|
Default is the containing BeanFactory's bean ClassLoader. |
|
|
|
|
org.mypackage), it will be resolved
from the classpath root.
Messages will normally be held in the "/lib" or "/classes" directory of a web application's WAR structure. They can also be held in jar files on the class path. Note that ResourceBundle names are effectively classpath locations: As a
consequence, the JDK's standard ResourceBundle treats dots as package separators.
This means that "test.theme" is effectively equivalent to "test/theme",
just like it is for programmatic |
org.mypackage),
it will be resolved from the classpath root.
The associated resource bundles will be checked sequentially when resolving a message code. Note that message definitions in a previous resource bundle will override ones in a later bundle, due to the sequential lookup. Note that ResourceBundle names are effectively classpath locations: As a
consequence, the JDK's standard ResourceBundle treats dots as package separators.
This means that "test.theme" is effectively equivalent to "test/theme",
just like it is for programmatic |
|
Default is the containing BeanFactory's bean ClassLoader , or the default ClassLoader determined by org.springframework.util.ClassUtils#getDefaultClassLoader() if not running within a BeanFactory. |
|