StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17147635
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-06-17T12:36:35.243
FavoriteCount
0
LastActivityDate
2013-06-17T13:24:28.317
LastEditDate
2013-06-17T13:24:28.317
LastEditorUserId
2410242
OwnerUserId
2410242
ParentId
14068525
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Currently it isn't possible to translate all XML-based AspectJ settings to a Java based configuration. Probably it will never be. The main reason is that Java doesn't support method literals. But there is a workaround, which was first presented here: <a href="https://jira.springsource.org/browse/SPR-8148" rel="nofollow">https://jira.springsource.org/browse/SPR-8148</a> <blockquote> <ol> <li>Continue using <code><aop:config></code> by including the relevant XML snippet using <code>@ImportResource</code></li> <li>Convert any existing <code><aop:config></code> elements to use <code>@Aspect</code> style.</li> </ol> </blockquote> Referring to the <a href="http://static.springsource.org/spring/docs/3.2.x/spring-framework-reference/html/aop.html#aop-ataspectj" rel="nofollow">documentation</a>, I would say that you're already nearly done with your configuration you have described above. You just have to change you config like this: <pre><code><aop:config> <aop:advisor id="managerTx" advice-ref="txAdvice" pointcut="com.myapp.configuration.AspectConfig.serviceAnnotatedClass()" order="20" /> </aop:config> </code></pre> Leave the rest like it is and import that resource: <pre><code>import org.aspectj.lang.annotation.Aspect; import org.aspectj.lang.annotation.Pointcut; @Aspect @ImportResource("classpath:/aop-config.xml") public class AspectConfig { @Pointcut("@within(org.springframework.stereotype.Service)") public void serviceAnnotatedClass() {} } </code></pre> I hope I could help...
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJavaConfig: Replacing aop:advisor and tx:advice
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USa.ha
UserOwnerUserId
1. USa.ha
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POJavaConfig: Replacing aop:advisor and tx:advice
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COthanks (especially for pointing out the jira-issue)!
 singulars
 PostPostId
 PO
 UserUserId
 USuser871611

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.