StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18579964
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-09-02T19:56:17.443
FavoriteCount
0
LastActivityDate
2013-09-02T19:56:17.443
LastEditDate
2017-05-23T12:20:18.343
LastEditorUserId
-1
OwnerUserId
157882
ParentId
18579680
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
It's because you're actually using an application scoped Spring managed bean instead of a request scoped JSF managed bean. Your main mistake is that you're mixing JSF bean management annotations with a Spring bean management annotation and somehow are expecting that they seamlessly understand each other. <pre><code>@Controller @ManagedBean @RequestScoped </code></pre> This is thus not true. You effectively end up with two completely independent managed bean instances, one managed by JSF and another managed by Spring. The <code>@RequestScoped</code> annotation is specific to JSF bean management facility. The Spring's equivalent, <code>@Scope("request")</code> is absent and therefore the Spring managed bean defaults to the application scope. When referencing the bean in EL scope like so <code>#{logInBean}</code>, the Spring managed one gets precedence over JSF managed one because of the Spring bean EL resolver and you ultimately end up with an application scoped Spring managed bean. This totally explains the symptoms. Fix it accordingly by getting rid of JSF bean management annotations and placing the desired Spring scope annotation: <pre><code>@Controller @Scope("request") </code></pre> (an alternative would be to get rid of Spring bean management annotation and replace <code>@Autowired</code> by <code>@EJB</code>, like as one would normally do when using standard Java EE stack without any 3rd party library) If you still face this problem, then another possible cause would be that you're submitting the login synchronously while not having <code>autocomplete="off"</code> on the input fields, head to this Q&A then: <a href="https://stackoverflow.com/questions/8504739/disable-web-browser-password-save">Disable web browser password save</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy does JSF form preserve values?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USBalusC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy does JSF form preserve values?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COGot it working by replacing JSF bean management annotations by Spring annotations. Thanks.
 singulars
 PostPostId
 PO
 UserUserId
 USperak
2. COYou're welcome.
 singulars
 PostPostId
 PO
 UserUserId
 USBalusC

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.