StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20168592
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-23T22:18:07.883
FavoriteCount
0
LastActivityDate
2013-11-23T22:18:07.883
LastEditDate
2017-05-23T11:51:55.010
LastEditorUserId
-1
OwnerUserId
1329290
ParentId
20149698
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I've acomplished question's goal. <code>@Ralph's</code> answer was very very helpfull, but to be precise I'll write what was needed more. I've created <code><a href="http://docs.spring.io/spring/docs/3.2.x/javadoc-api/org/springframework/web/method/support/HandlerMethodArgumentResolver.html" rel="nofollow noreferrer">HandlerMethodArgumentResolver</a></code>, name it <code>CustomHandlerMethodArgumentResolver</code>. To map all request parameters to result object, I had to mark controller's method's param as <code>@RequestBody</code>. That was not enough because Spring's default <code>HandlerMethodArgumentResolvers</code> try to map it first and my resolver wasn't executed. But <a href="https://stackoverflow.com/a/19847526/1329290">this</a> answer pointed how to set priority for my resolver. <code>@PostConstruct</code> did not work (not shure why), so I've modified my <code>@Configuration</code> class to implement <code>ApplicationListener<ContextRefreshedEvent></code>. Here is the code: <pre><code>@Override public void onApplicationEvent(ContextRefreshedEvent event) { RequestMappingHandlerAdapter adapter = event.getApplicationContext().getBean( RequestMappingHandlerAdapter.class); CustomHandlerMethodArgumentResolver resolver = event.getApplicationContext().getBean( CustomHandlerMethodArgumentResolver.class); List<HandlerMethodArgumentResolver> argumentResolvers = new ArrayList<>( adapter.getArgumentResolvers().getResolvers()); List<HandlerMethodArgumentResolver> customResolvers = adapter.getCustomArgumentResolvers(); argumentResolvers.remove(resolver); argumentResolvers.add(0, resolver); adapter.setArgumentResolvers(argumentResolvers); } </code></pre> Of course <code>CustomHandlerMethodArgumentResolver</code> <code>.supportsParameter(MethodParameter)</code> checks if actual situation should be processed in custom or default way - that depends on requirements. Thank you <code>@Ralph</code> for lightning fast help!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConvert request params to generic class
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. UStunguski
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
 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.