Q. You can define a locale resolver by registering a bean of type LocaleResolver in the web application context.

View solution

Q. Default localeResolver used by Spring.

View solution

Q. AcceptHeaderLocaleResolver resolves locales by inspecting the accept-language header of an HTTP request.

View solution

Q. Alternative way to resolve locales.

View solution

Q. Property which indicates how many seconds this cookie should be persisted.

View solution

Q. Method used to change user’s locale.

View solution

Q. Property of LocaleChangeInterceptor used to customize parameter name.

View solution

Q. LocaleChangeInterceptor can only detect the parameter for the handler mappings that enable it.

View solution

Q. Parameter which can change user’s locale by any URL.

View solution

Q. Interface used to resolve text messages.

View solution

Q. Tag used by view to resolve text messages.

View solution

Q. The ResourceBundleMessageSource implementation resolves messages for different locales.

View solution

Q. cookieName is used by localeResolver to customize the cookie used.

View solution

Q. The cookieMaxAge value when browser is closed.

View solution

Q. Interface for Dispatcher Servlet to auto detect view resolver beans.

View solution

Q. ViewResolver which maps each view name tol an application’s directory.

View solution

Q. InternalResourceViewResolver resolves view names into view objects of type.

View solution

Q. By default, XmlViewResolver loads view beans from /WEB-INF/views.xml which is final.

View solution

Q. View beans from a resource bundle is loaded by.

View solution

Q. Views that can’t be resolved by InternalResourceViewResolver.

View solution