StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7969261
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-01T16:04:53.677
FavoriteCount
0
LastActivityDate
2011-11-01T16:04:53.677
LastEditDate
LastEditorUserId
0
OwnerUserId
566763
ParentId
2130683
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<code>formBackingObject()</code> is expected to set up the "command" Object that is supplied to <code>onSubmit()</code> on the next submission. The command Object is just a <a href="http://en.wikipedia.org/wiki/Plain_Old_Java_Object" rel="nofollow">POJO</a> that you can create and add attributes to as needed. Normally you populate the command Object with some data to be displayed on the screen from a service call (which ultimately comes from the DB) but there's nothing to stop you placing data that arrived in the request in <code>formBackingObject()</code> into the command Object and pulling it back off again when <code>onSubmit()</code> is called. The advantage of doing this is that you don't end up with <a href="http://en.wiktionary.org/wiki/cruft" rel="nofollow">cruft</a> floating around in your session. For example, put a boolean from the request in <code>MyCommand</code> in <code>formBackingObject()</code>: <pre><code> protected Object formBackingObject(HttpServletRequest request) { boolean someBoolean = ServletRequestUtils.getBooleanParameter(request, "someBoolean"); MyCommand myCommand = new MyCommand(); myCommand.setSomeBoolean(someBoolean); // optionally get some data from the DB to set on myCommand here... return myCommand; } </code></pre> Then find that boolean inside the request in <code>onSubmit()</code>: <pre><code> protected ModelAndView onSubmit(HttpServletRequest request, HttpServletResponse response, Object command, BindException errors) { MyCommand myCommand = (MyCommand) command; if (myCommand.getSomeBoolean()) { System.out.println("someBoolean was set in formBackingObject!"); } } </code></pre> Note that myCommand is only visible to the session (so no other logged in users can see it, and it is destroyed when the session ends).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSpring SimpleFormController onSubmit request parameters
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRedYeti
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. This table or related slice is empty.
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.