StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11158151
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-22T14:26:42.790
FavoriteCount
0
LastActivityDate
2012-06-22T14:26:42.790
LastEditDate
LastEditorUserId
0
OwnerUserId
1332414
ParentId
11156836
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
You could use <a href="http://docs.jboss.org/weld/reference/1.0.0/en-US/html/interceptors.html" rel="nofollow">CDI's interceptor annotations</a> and do something like: <pre><code>... @Validated public String sayHello(@Validator(MyValidator.class) String name) { ... </code></pre> Where <code>@Validated</code> binds the method to a <code>ValidationInterceptor</code> class or so, where you use an <code>@AroundInvoke</code> method and its <code>InvocationContext</code> parameter to inspect the passed parameters and validate them. One "difficulty" with this approach is that you will have to use reflection to get the <code>@Validator</code> annotation and specified validator class for each parameter, then create/retrieve corresponding instances before you can finally do the actual validation. A slightly different approach would be to inject an <code>Instance<T></code> of a common superclass/interface of your validators into the <code>ValidationInterceptor</code> and annotate the <code>sayHello</code> parameters with validator qualifiers: <pre><code>// in ValidationInterceptor: @Inject private Instance<Validator> validatorInstance; @AroundInvoke public Object validate(InvocationContext context) { // get Annotation instances for target method parameters // ... Validator validator = validatorInstance.select(annotations).get(); // ... validator.validate(parameter); ... } // sayHello: ... @Validated public String sayHello(@NameValidator String name) { ... </code></pre> To get parameter annotations from <code>InvocationContext</code>, do something like: <pre><code>Annotation[][] annotations = context.getMethod().getParameterAnnotations(); </code></pre> You may also consider pre-processing these annotations in an <code>@AfterBeanDiscovery</code> event handler.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCDI validation on received parameter
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTorious
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
2. 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.