StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18917442
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-09-20T13:00:00.417
FavoriteCount
0
LastActivityDate
2017-03-14T07:25:25.563
LastEditDate
2017-03-14T07:25:25.563
LastEditorUserId
3850730
OwnerUserId
1073995
ParentId
16062922
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
Within Spring Batch Admin, there are 2 Spring ApplicationContexts that are being loaded: <ul> <li>servlet-config.xml</li> <li>webapp-config.xml</li> </ul> servlet-config.xml has these imports: <pre><code><import resource="classpath*:/META-INF/spring/batch/servlet/resources/*.xml" /> <import resource="classpath*:/META-INF/spring/batch/servlet/manager/*.xml" /> <import resource="classpath*:/META-INF/spring/batch/servlet/override/*.xml" /> </code></pre> webapp-config.xml has these imports: <pre><code><import resource="classpath*:/META-INF/spring/batch/bootstrap/**/*.xml" /> <import resource="classpath*:/META-INF/spring/batch/override/**/*.xml" /> </code></pre> servlet-config.xml configurers the servlet, webapp-config.xml configures (the backend part of the) the application. The problem is that the dataSource bean is part of/defined in the second config, not the first. Hence, when you add the dataSource bean to an override for the servlet config(/META-INF/spring/batch/servlet/override/*.xml), as you are doing, you add a new bean to the first context, instead of overwriting the dataSource bean of the second context. So, you need to put your custom data-source-context.xml under META-INF/spring/batch/override/ instead of META-INF/spring/batch/servlet/override/ Then it works and you won't even get the <code>Could not resolve placeholder 'batch.jdbc.driver' in string value [${batch.jdbc.driver}]</code> error.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing jndi datasource with spring batch admin
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USIntegrating Stuff
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing jndi datasource with spring batch admin
 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. 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.