|
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Pradeep, What exactly do you mean by connection Pooling ?
can you elaborate this with an example.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
I got a new error in my application.
It is saying "SQLException : Driver not found".
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Then what in case of a session bean the difference in using Class.forName(..) type connection and DataSource type connection.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Pradeep Bhat:
Can you tell us which app server you are using?
Originally posted by Pradeep Bhat:
I understood you problem. The reason I asked abt the app server is because you are facing "Driver not found". Is it J2EE RI from Sun?
Originally posted by Pradeep Bhat:
RI stands for the reference implementation. I have a question - Where have you placed your driver class jar file.
Originally posted by Pradeep Bhat:
The problem is you driver class files are not in the classpath. The j2ee server from Sun comes with only cloudscape driver. I guess you can use the JDBC-ODBC (type 1) driver. It comes along with the JDK.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Lasse Koskela:
Venkatesh, which database you're using? The Cloudscape that comes with J2EE RI? If so, then the driver should already be configured according to the documentation (<J2EE_HOME>/doc/release/ConfigGuide.html#12442).
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Lasse Koskela:
Hmm. If you're using the Sun JDBC-ODBC bridge, you shouldn't need any configuration either according to Sun's documentation.
Maybe you should check that you have JdbcOdbc.dll under your JRE directory?
You did say of mapping the datasource with deploytool.
well,i provided a jndi name "jdbc/sqlServer" in the resource references.
I have used the same datasource name in the code "java:comp/env/jdbc/Manifestation"
Then in the default.properties file i have mentioned "jdbc.datasources = jdbc/sqlServer|jdbc dbc:Manifestation"
then why am i getting this error : java.sql.SQLException : Driver Not Found
Waiting for your Reply.............
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Yes, of course, and I accept that blame. In fact, i covet that blame. As does this tiny ad:
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
|