TCK Challenge: JDBC Client Apps are missing DataSource refs #2414
Description
Challenged Tests:
com.sun.ts.tests.jdbc.ee.callStmt.callStmt1.callStmtClient1AppClient
com.sun.ts.tests.jdbc.ee.callStmt.callStmt1.callStmtClient1EJB
com.sun.ts.tests.jdbc.ee.callStmt.callStmt10.callStmtClient10AppClient
TCK Version:
Jakarta EE Platform TCK 11.0.x
Tested Implementation:
Open Liberty
Description:
callStmtClient1AppClient and callStmtClient10AppClient each have incorrect paths to their application client xml files, so the constructed apps end up not having the necessary resource-refs for the DataSource under test. As a result, the tests can fail in setup attempting to lookup the DataSource.
08-25-2025 04:29:56: ERROR: Setup Failed!
08-25-2025 04:29:56: ERROR: javax.naming.NameNotFoundException: javax.naming.NameNotFoundException: java:comp/env/jdbc/DB1
at com.ibm.ws.jndi.url.contexts.javacolon.internal.JavaURLContext.lookup(JavaURLContext.java:357)
at [internal classes]
at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)
at com.sun.ts.lib.util.TSNamingContext.lookup(TSNamingContext.java:63)
at com.sun.ts.tests.jdbc.ee.common.DataSourceConnection.getConnection(DataSourceConnection.java:46)
at com.sun.ts.tests.jdbc.ee.callStmt.callStmt1.callStmtClient1.setup(callStmtClient1.java:112)
...
callStmtClient1EJB has some tests improperly marked as appclient. Those tests can fail the same way as above for the same reason.
These (and other) tests have been fixed in the main branch with PR #2413