StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8135301
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-11-15T11:01:38.320
FavoriteCount
0
LastActivityDate
2013-03-25T12:34:46.123
LastEditDate
2013-03-25T12:34:46.123
LastEditorUserId
322166
OwnerUserId
998692
ParentId
8134720
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You must have an interceptor in applicationContext like <pre class="lang-xml prettyprint-override"><code><mvc:interceptors> <bean class="org.springframework.web.servlet.i18n.LocaleChangeInterceptor"> <property name="paramName" value="lang" /> </bean> </mvc:interceptors> </code></pre> You also need <pre class="lang-xml prettyprint-override"><code><bean id="messageSource" class="org.springframework.context.support.ReloadableResourceBundleMessageSource"> <property name="basename" value="classpath:messages" /> <property name="defaultEncoding" value="UTF-8" /> </bean> <bean id="localeResolver" class="org.springframework.web.servlet.i18n.SessionLocaleResolver"/> </code></pre> On the first JSP page of my project I gave a choice for languages like that: <pre class="lang-html prettyprint-override"><code> <a href="?lang=en">en</a> | <a href="?lang=fr">fr</a> </code></pre> Please tell me if this helped you. P.S. My messages_*.properties files are in a source folder src/main/resources, not in webapp, I don't know if this matters. P.P.S. Useful tutorial here: <a href="http://springbyexample.org/examples/basic-webapp-internationalization.html" rel="nofollow">http://springbyexample.org/examples/basic-webapp-internationalization.html</a> I would like to add also that at the beginning of your xml you should have stuff like: <pre class="lang-xml prettyprint-override"><code><beans xmlns="http://www.springframework.org/schema/beans" xmlns:tx="http://www.springframework.org/schema/tx" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="http://www.springframework.org/schema/p" xmlns:mvc="http://www.springframework.org/schema/mvc" xmlns:context="http://www.springframework.org/schema/context" xmlns:util="http://www.springframework.org/schema/util" xmlns:security="http://www.springframework.org/schema/security" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.0.xsd http://www.springframework.org/schema/mvc http://www.springframework.org/schema/mvc/spring-mvc-3.0.xsd http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util-3.0.xsd http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-3.0.xsd"> </code></pre> It is necessary in order to recognize the prefixes such as mvc. Make sure you have it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSpring MVC - fetching wrong message bundle
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDani
UserOwnerUserId
1. USuser998692
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTApproveEditSuggestion
CommentsPostId
1. COproperty name="basename" or **basenames**?
 singulars
 PostPostId
 PO
 UserUserId
 USQueequeg
2. COIt's basename, not basenames.
 singulars
 PostPostId
 PO
 UserUserId
 USuser998692

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.