StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9331400
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-17T15:54:50.670
FavoriteCount
0
LastActivityDate
2017-11-14T23:53:03.320
LastEditDate
2017-11-14T23:53:03.320
LastEditorUserId
192465
OwnerUserId
873530
ParentId
880746
PostTypeId
2
Score
22
ViewCount
0
LastEditorDisplayName
text
Body
There is a big debate on whether the session attributes are cleared after controller exit. To clarify once and for all, we can look at the Spring MVC 3.1.0 RELEASE source code. The interface org.springframework.web.bind.support.SessionAttributeStore exposes the following methods: <pre><code>void storeAttribute(WebRequest request, String attributeName, Object attributeValue); Object retrieveAttribute(WebRequest request, String attributeName); void cleanupAttribute(WebRequest request, String attributeName); </code></pre> The default implementation is org.springframework.web.bind.support.DefaultSessionAttributeStore By doing a "Open Call Hierarchy" on cleanupAttribute() in Eclipse, we can see that the method is called by 2 different flows: 1) org.springframework.web.method.annotation.ModelFactory <pre><code>public void updateModel(NativeWebRequest request, ModelAndViewContainer mavContainer) throws Exception { if (mavContainer.getSessionStatus().isComplete()){ this.sessionAttributesHandler.cleanupAttributes(request); } else { this.sessionAttributesHandler.storeAttributes(request, mavContainer.getModel()); } if (!mavContainer.isRequestHandled()) { updateBindingResult(request, mavContainer.getModel()); } } </code></pre> 2) org.springframework.web.bind.annotation.support.HandlerMethodInvoker <pre><code>public final void updateModelAttributes(Object handler, Map<String, Object> mavModel, ExtendedModelMap implicitModel, NativeWebRequest webRequest) throws Exception { if (this.methodResolver.hasSessionAttributes() && this.sessionStatus.isComplete()) { for (String attrName : this.methodResolver.getActualSessionAttributeNames()) { this.sessionAttributeStore.cleanupAttribute(webRequest, attrName); } } ... } </code></pre> It is clear that in both cases, the session attribute is removed only when this.sessionStatus.isComplete() is called. I dug into the code of DefaultSessionAttributeStore. Under the hood, it gets the real HTTP Session object to store attributes, so they can potentially be accessed by other controllers in the same session. So no, the session attributes are not removed after a clean POST.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat happens if I forget to mark the Spring SessionStatus as "Complete"?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USbphilipnyc
UserOwnerUserId
1. USdoanduyhai
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
 VTUndeletion
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.