well,
you still need to declare the JDBC driver in the "JDBC MBean" thingy.
That is one of the things that we need to change, to have the connector
declare what driver he is using as opposed to the kludgy MBean we have right
now as a front end to loading the drivers.
marcf
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Vincent Harcq
|Sent: Wednesday, September 05, 2001 1:01 PM
|To: Dev JBoss
|Subject: [JBoss-dev] Jboss 3.0 / DataSource problem
|
|
|Hi,
|Running latest JBoss 3.0,
|I have defined a datasource based on Opta2000 driver for MS SQL.
|I have added the driver to the list of JDBC driver and the opta JAR to the
|list of jar in top of jboss-service.xml.
|I used the new way of configuring the pool, I simply copy/paste the one of
|DefaultDS and changed the minimum.
|
|I got this exception while deploying an entity Bean.
|
|[JDBCManagedConnectionFactory-1] Unable to create ManagedConnection:
|javax.resource.ResourceException: Unable to create DB connection:
|java.sql.SQLException: No suitable driver
| at
|org.jboss.pool.connector.jdbc.JDBCManagedConnectionFactory.createMa
|nagedConn
|ection(JDBCManagedConnectionFactory.java:245)
|
|Does this say something to somebody ?
|
|Thanks.
|Vincent.
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
