Introducing Spring Framework

Chapter 10 ■ Showing Your Spring Application on the Web
select d.documentId, d.name, d.location, d.description as doc_desc,
d.typeId, d.created, d.modified,
t.name as type_name, t.description as type_desc, t.extension from
documents d
join types t
on d.typeId = t.typeId
In Listing 10-8, you add an interceptor the LocaleChangeInterceptor. It will help you with a parameter
named lang to change the locale. (If omitted, the default parameter will be locale.) Next, you have the
ReloadableResourceBundleMessageSource class, which helps you find the path where your bundle message
will be. In your case, WEB-INF/i18n/ is the path and messages is the name of the bundle. Also, you are defining a
CookieLocaleResolver that will help you to save the state of your locale selected during your session.
After modifying the XML file, you need to add the messages.properties file with its translations. In Chapter 6, I talked
about using resource files. In this example, you will be using Spanish. You are going to create three files, one of which
will be the default: messages.properties, messages_en.properties (for English), and messages_es.properties
(for Spanish). Listing 10-9, 10-10, and 10-11 contain the messages bundles.
Listing 10-9. WEB-INF/i18n/messages.properties
main.title=Welcome to My Documents
search.subtitle=.:: My Documents - Search ::.
search.name=Name:
search.type=Type:
search.location=Location:
Listing 10-9 shows the default message.properties file. Now let’s take a look at the English properties.
See Listing 10-10.
Listing 10-10. WEB-INF/i18n/messages_en.properties
main.title=Welcome to My Documents
search.subtitle=.:: My Documents - Search ::.
search.name=Name:
search.type=Type:
search.location=Location:
142