StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19892761
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
2013-11-13T01:07:49.353
CreationDate
2013-11-10T17:31:02.207
FavoriteCount
0
LastActivityDate
2013-11-10T17:42:23.497
LastEditDate
2013-11-10T17:42:23.497
LastEditorUserId
2964890
OwnerUserId
2964890
ParentId
19734175
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Will you please update your question with ready-to-go compilable code. Here's some code review suggestions: Issues with this question code: <ul> <li>Article.java missing import: org.springframework.beans.factory.annotation.Autowired</li> <li>Article.java missing import: org.springframework.transaction.annotation.Transactional</li> <li>Article.java attribute syntax issue: dbRequestHandler</li> <li>Article.java attribute syntax issue: filesystemRequestHandler</li> <li>Article.java method has no initialized return statement: articleDTO</li> </ul> Here's what you maybe should use as you questionCode with the above issues fixed: Article.java <pre><code>import org.springframework.beans.factory.annotation.Autowired; import org.springframework.transaction.annotation.Transactional; public class Article { @Autowired private Object dbRequestHandler; @Autowired private Object filesystemRequestHandler; @Transactional public ArticleDTO getArticleContents() { // extractText() and then save the data in DTO // extractImages() and then save the data in DTO // some other calls to other databases to save data in dto ArticleDTO articleDTO = null; return articleDTO; } public void extractText() { // call to DB } public void extractImages() { // call to file system } } </code></pre> IntegrationTest.java is a poor name for a testClass because it's to generic. I would suggest ArticleTest for a java unit test. ArticleTest.java <pre><code>import org.junit.Assert; import org.junit.Test; import org.junit.runner.RunWith; import org.mockito.InjectMocks; import org.mockito.Mock; import org.mockito.Mockito; import org.powermock.core.classloader.annotations.PrepareForTest; import org.powermock.modules.junit4.PowerMockRunner; import org.springframework.beans.factory.annotation.Autowired; @RunWith(PowerMockRunner.class) @PrepareForTest(ClassWithPrivate.class) public class ArticleTest { @InjectMocks private Article cut; @Mock private Object dbRequestHandler; @Mock private Object filesystemRequestHandler; @Test public void testeExtractImages() { /* Initialization */ Article articleMock = Mockito.spy(cut); /* Mock Setup */ Mockito.doNothing().when(articleMock).extractImages(); /* Test Method */ ArticleDTO result = cut.getArticleContents(); /* Asserts */ Assert.assertNull(result); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMocking CGLIB enhanced objects
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USjavaPlease42
UserOwnerUserId
1. USjavaPlease42
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. 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.