StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POJNDI Resource Definition in Apache Tomcat 6
primarykey
Id
10137828
data
AcceptedAnswerId
10138496
AnswerCount
1
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-04-13T08:47:22.200
FavoriteCount
0
LastActivityDate
2013-10-02T06:25:50.843
LastEditDate
LastEditorUserId
0
OwnerUserId
1221053
ParentId
0
PostTypeId
1
Score
0
ViewCount
5579
LastEditorDisplayName
text
Body
I'm more than inexperienced with Apache Tomcat, so forgive me if it's a trivial question I'm asking. My task is to change a rather big program so that it uses the connection from Tomcat instead of its own bean, so that you don't have to rebuild the code when the database changes. This is the original bean definition (slightly changed - passwords and such...): <pre><code><bean id="ProjectDS" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close" scope="singleton"> <property name="url" value="jdbc:as400://127.0.0.1/TEST2;prompt=false;naming=sql;errors=full;date format=usa;date separator=/;time format=hms;time separator=:;transaction isolation=read committed;"/> <property name="driverClassName" value="com.ibm.as400.access.AS400JDBCDriver"/> <property name="username" value="asdf"/> <property name="password" value="asdf"/> <property name="initialSize" value="${ProjectDS.initialSize}"/> <property name="maxActive" value="${ProjectDS.maxActive}"/> <property name="maxIdle" value="${ProjectDS.maxIdle}"/> <property name="minIdle" value="${ProjectDS.minIdle}"/> <property name="testOnBorrow" value="${ProjectDS.testOnBorrow}"/> <property name="removeAbandoned" value="${ProjectDS.removeAbandoned}"/> <property name="removeAbandonedTimeout" value="${ProjectDS.removeAbandonedTimeout}"/> <property name="logAbandoned" value="${ProjectDS.logAbandoned}"/> </bean> </code></pre> After reading several tutorials about Tomcat configuration, I did the following: The new bean: <pre><code><bean id="ProjectDS" class="org.springframework.jndi.JndiObjectFactoryBean"> <property name="jndiName"> <value>ProjectDS</value> </property> <property name="resourceRef" value="true"></property> </bean> </code></pre> server.xml : <pre><code><Resource name="ProjectDS" global="ProjectDS" auth="Container" type="org.apache.commons.dbcp.BasicDataSource" driverClassName="com.ibm.as400.access.AS400JDBCDriver" url="jdbc:as400://127.0.0.1/TEST2" username="asdf" password="asdf" /> </code></pre> context.xml: <pre><code><WatchedResource>WEB-INF/web.xml</WatchedResource> <ResourceLink global="ProjectDS" name="ProjectDS" type="org.apache.commons.dbcp.BasicDataSource"/> </code></pre> What I get is: <blockquote> Exception processing Global JNDI Resources javax.naming.NamingException: Cannot create resource instance </blockquote> I read somewhere that I shouldn't put the above into the server.xml but into the web.xml, but I don't know where exactly. Could that be the problem? 
Tags
<spring><tomcat6><jndi>
Title
JNDI Resource Definition in Apache Tomcat 6
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMahawkee
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COI found this other solution: http://stackoverflow.com/questions/9841109/how-to-change-spring-to-use-datasource-from-tomcat-vs-basicdatasource but it also gives me error messages (Error listenerStart) when I try it that way.
 singulars
 PostPostId
 POJNDI Resource Definition in Apache Tomcat 6
 UserUserId
 USMahawkee

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.