Thanks, Antonio, with all my regards!
2007/10/22, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]>: > > All jars. It is the axis classpath. > > Antonio. > > 2007/10/22, Qil. Wong <[EMAIL PROTECTED]>: > > > > Thanks,Antonio! > > > > Another question: should all the third party libraries used in the > > project be put into /axis2/WEB-INF/lib? or only the drivers? > > > > > > 2007/10/22, Antonio Manuel Muñiz Martín < [EMAIL PROTECTED]>: > > > > > > Put the db driver .jar in /axis2/WEB-INF/lib, all jars what you want > > > to use must go here. > > > > > > 2007/10/22, Qil. Wong < [EMAIL PROTECTED]>: > > > > > > > > Hi, > > > > > > > > I have one javase application and now I need to change it into > > > > axis2 webservice and publish it. > > > > > > > > While it was javase application, it run fine(certanlly, it could > > > > db connections). But after I change it into axis2 service, when the > > > > application tries to create database connection, there will be an > > > > exception > > > > : no suitable driver. Actually, all the jdbc libs needed are in > > > > classpath. > > > > > > > > My method to get connection is from a common database pool(with > > > > apache libs:common-dbcp.jar,common-pool.jar), the database is > > > > sqlserver2000. If I get the connection directly by using: > > > > Class.forName(...), Connection conn = > > > > DriverManager.getConnection(url,name,psw), > > > > I could get the connection successfully. > > > > > > > > Could anyone tell me how to solve it by using database > > > > connection pool? > > > > > > > > > > > > >
