StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18153348
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-09T18:31:41.843
FavoriteCount
0
LastActivityDate
2013-08-09T18:37:46.993
LastEditDate
2013-08-09T18:37:46.993
LastEditorUserId
1666206
OwnerUserId
1666206
ParentId
18087308
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I found my answer. The problem with my unit test is that I was using: <pre><code> @ContextConfiguration(locations = {"classpath*:project-infrastructure.xml","classpath*:applicationContext.xml"}) </code></pre> which means this was pulling in the completely wrong applicationContext.xml file, and the wrong project-infrastructure.xml file. In my Spring DAO app, I made sure I was using an app context file specifically to this project, so I renamed it a unique name: myproject1-app-context.xml and myproject1-infrastructure.xml file. In this maven project, the directory structure looks like: src/main/java src/main/resources src/main/resources/spring <-- where my spring app context files are located In the unit test I changed the location to: <pre><code>@ContextConfiguration(locations = {"classpath:/spring/myproject1-infrastructure.xml", "classpath:/spring/myproject1-app-context.xml"}) </code></pre> And once I did that, I stopped getting the autowired error. I know there is some code or trick to point out the files in my classpath that are being used. I should use that someday, but at least this solved my problem. As was previously stated, using @Repository in the DAO class, and removing the definition from the myproject1-app-context.xml file, and I did include: <pre><code>  <context:annotation-config />  <context:component-scan base-package="com.tom.project" /> </code></pre> This was included in the myproject1-app-context.xml file. So, I hope this helps someone out sometime ....
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSpring Autowired DAO with hibernate.cfg.xml
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UStjholmes66
UserOwnerUserId
1. UStjholmes66
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSpring Autowired DAO with hibernate.cfg.xml
 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
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.