StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7982826
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-02T15:22:05.933
FavoriteCount
0
LastActivityDate
2011-11-02T15:22:05.933
LastEditDate
LastEditorUserId
0
OwnerUserId
0
ParentId
6770156
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
IMHO one could think about the Visitor pattern in combination with a factory. The factory will return a wrapper object that knows the exact annotation type and which the visitor will be able... <pre><code>class MyVisitor { public void visit(VisitableAnnotationType1 at) { //something AnnotationType1 specific } public void visit(VisitableAnnotationType2 at) { //something AnnotationType2 specific } ... // put methods for further annotation types here } class VisitableFactory { public abstract class VisitableAnnotation { public abstract void accept(MyVisitor visitor); } class VisitableAnnotationType1 implements VisitableAnnotation { public void accept(MyVisitor visitor) { visitor.visit(this); } } public static VisitableAnnotation getVisitable(Annotation a) { if(AnnotationType1.class.isAssignableFrom(a.getClass()) { //explicitely cast to the respective AnnotationType return new VisitableAnnotationType1((AnnotationType1)a); } else if (AnnotationType2.class.isAssignableFrom(a.getClass()) { //explicitely cast to the respective AnnotationType return new VisitableAnnotationType1((AnnotationType1)a); } } } </code></pre> As we cannot extend Annotation, we need those wrapper classes in the factory. You could also pass the original annotation which is then contained in that wrapper class. What you have to do: For each new AnnotationType add a new "wrapper" class to the factory, extend the factory's <pre><code>getVisitable() </code></pre> method accordingly and also add an according method to the Visitor: <pre><code>public void doSomething(VisitableAnnotationTypeXYZ at) { //something AnnotationTypeXYZ specific } </code></pre> now the generic validation (or whatever) code looks like: <pre><code>List<ValidatableAnnotation> annotations = mergeConstraintsFromClassAndMethod(serviceClass, serviceMethod); MyVisitor visitor = new MyVisitor(); for (ValidatableAnnotation annotation : annotations) { VisitableFactory.getVisitable(annotation).accept(visitor); } </code></pre> The visiting works by the indirection that the visited object calls the visitor with itself as the argument and thus the correct visit method will be invoked. Hope that helps ;-) Code is not tested, though...
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs this a good pattern for annotation processing?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. This table or related slice is empty.
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.