From 8a9321652d45b6a524921e2cc5988696495ecaaa Mon Sep 17 00:00:00 2001 From: Juergen Hoeller Date: Sat, 31 Mar 2018 23:07:08 +0200 Subject: [PATCH] Refined javadoc --- .../web/servlet/view/ResourceBundleViewResolver.java | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/spring-webmvc/src/main/java/org/springframework/web/servlet/view/ResourceBundleViewResolver.java b/spring-webmvc/src/main/java/org/springframework/web/servlet/view/ResourceBundleViewResolver.java index f9783feaf82..a0dc4417a24 100644 --- a/spring-webmvc/src/main/java/org/springframework/web/servlet/view/ResourceBundleViewResolver.java +++ b/spring-webmvc/src/main/java/org/springframework/web/servlet/view/ResourceBundleViewResolver.java @@ -89,7 +89,7 @@ public class ResourceBundleViewResolver extends AbstractCachingViewResolver /** * Set a single basename, following {@link java.util.ResourceBundle} conventions. * The default is "views". - *

{@code ResourceBundle} supports different suffixes. For example, + *

{@code ResourceBundle} supports different locale suffixes. For example, * a base name of "views" might map to {@code ResourceBundle} files * "views", "views_en_au" and "views_de". *

Note that ResourceBundle names are effectively classpath locations: As a @@ -107,19 +107,19 @@ public class ResourceBundleViewResolver extends AbstractCachingViewResolver /** * Set an array of basenames, each following {@link java.util.ResourceBundle} * conventions. The default is a single basename "views". - *

{@code ResourceBundle} supports different suffixes. For example, + *

{@code ResourceBundle} supports different locale suffixes. For example, * a base name of "views" might map to {@code ResourceBundle} files * "views", "views_en_au" and "views_de". - *

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. + *

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 {@code java.util.ResourceBundle} usage. * @see #setBasename * @see ResourceBundle#getBundle(String) + * @see ResourceBundle#getBundle(String, Locale) */ public void setBasenames(String... basenames) { this.basenames = basenames;