StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
780775
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-04-23T08:19:57.027
FavoriteCount
0
LastActivityDate
2011-11-03T17:14:48.717
LastEditDate
2011-11-03T17:14:48.717
LastEditorUserId
18122
OwnerUserId
18122
ParentId
768063
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
It depends on what style of AOP you choose with Spring. As you stick with the annotation based approach, there is not much you can get except having constants for the expressions located in an extenal class. This is due to the @Aspect annotation based AOP style dedicated to colocate where and what. You can somehow get some configurability by using abstract method and binding the pointcut to it. <pre><code>@Aspect public abstract class MyAspect { protected abstract pointcut(); @Before("pointcut()") public void myAdviceMethod() { // Advice code goes here } } public class ConcreteAspect extends MyAspect { @Pointcut("execution(* com.acme.*.*(..))") protected pointcut() { ) } </code></pre> This is possible but seems rather awkward to me as the implementor has to know that <code>@Pointcut</code> is required on the method. If she forgets to place it, it will crash entirely. If you need the flexibility to have advice and pointcut separated you better stick to the XML based configuration (see <a href="http://static.springframework.org/spring/docs/2.5.x/reference/aop.html#aop-schema" rel="nofollow noreferrer">Spring documentation</a> for example). A kind of man in the middle is the possibility to tie your pointcut to a custom annotation and let the users decide where to place it and thus, when to get your advice applied. <a href="http://static.springframework.org/spring/docs/2.5.x/reference/aop.html#aop-pointcuts" rel="nofollow noreferrer">Spring documentation (chapter 6.2.3.4)</a> gives more info on that. Regards, Ollie
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAvoiding in-place pointcut expression in Spring AOP
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USOliver Gierke
UserOwnerUserId
1. USOliver Gierke
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAvoiding in-place pointcut expression in Spring AOP
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.