StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18461133
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-27T08:57:35.290
FavoriteCount
0
LastActivityDate
2013-08-27T09:07:18.877
LastEditDate
2013-08-27T09:07:18.877
LastEditorUserId
2696260
OwnerUserId
2696260
ParentId
18380595
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Make sure that you don't have exact duplicate <code><context:component-scan .../></code> elements in both xml configurations. If you have this you are basically duplicating all your bean instances. What you initially had was all beans get loaded by the <code>ContextLoaderListener</code> and those are proxied due to the existence of <code><tx:annotation-driven /></code>. Now if you have the same <code><context:component-scan .../></code> in your payment-servlet.xml this is going to scan again for all beans creating another instance, however due to the fact that there is no <code><tx:annotation-driven /></code> it will not be proxied and no transactions applied. What now happens is that as soon as you need one of your <code>@Service</code> annotated beans the <code>DispatcherServlet</code> looks first in its own <code>ApplicationContext</code> to see if there is bean to satisfy its needs. If there is it is going to be used (your current case) if there isn't it will consult the parent context (the one loaded by the <code>ContextLoaderListener</code>). What you need to do is configure the <code>ContextLoaderListener</code> to scan for everything BUT <code>@Controller</code> annotated beans and the <code>DispatcherServlet</code> to scan ONLY for <code>@Controller</code> annotated beans. This can be done by configuring the <code><context:component-scan .../></code> correctly. applicationContext.xml <pre><code><context:component-scan base-package="com.appn.payment"> <context:exclude-filter type="annotation" expression="org.springframework.stereotype.Controller" /> </context:component-scan> </code></pre> payment-servlet.xml <pre><code><context:component-scan base-package="com.appn.payment" use-default-filters="false"> <context:include-filter type="annotation" expression="org.springframework.stereotype.Controller" /> </context:component-scan> </code></pre> This will give you transactions and only single instances of your beans. You should remove the <code><tx:annotation-driven /></code> from the payment-servlet.xml file. There is still an open <a href="https://jira.springsource.org/browse/SPR-6803?page=com.googlecode.jira-suite-utilities%3atransitions-summary-tabpanel" rel="nofollow">JIRA issue</a> to have this included in the reference guide. Also a thread in the <a href="http://forum.springsource.org/showthread.php?84265-Why-is-TransactionSynchronizationManager-not-being-activited&p=282436#post282436" rel="nofollow">Spring Community Forums</a> explaining this.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSpring application doesn't appear to be persisting data
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USM. Deinum
UserOwnerUserId
1. USM. Deinum
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSpring application doesn't appear to be persisting data
 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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTBountyClose
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.