[jboss-jira] [JBoss JIRA] Updated: (JBAS-5035) MySQLValidConnectionChecker has driver name com.mysql.jdbc.Driver hard coded
[ http://jira.jboss.com/jira/browse/JBAS-5035?page=all ]
Adrian Brock updated JBAS-5035:
-------------------------------
Issue Type: Feature Request (was: Bug)
Assignee: (was: Weston Price)
Priority: Minor (was: Major)
I don't see how this is a bug. There are many checkers for many different
drivers/databases.
This one was contributed by somebody that used a specific MySQL driver.
In fact, they got MySQL to implement the feature so they could write the checker in the
first place.
Write your own checker for the other driver and contribute it back.
If you want to contribute one that uses java.sql.Connection.isValid() (Java6 only)
that would be nice as well.
Leaving this open as a feature request for somebody that does want to contribute.
MySQLValidConnectionChecker has driver name com.mysql.jdbc.Driver
hard coded
----------------------------------------------------------------------------
Key: JBAS-5035
URL: http://jira.jboss.com/jira/browse/JBAS-5035
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.0.GA, JBossAS-4.0.5.GA
Environment: Any
Reporter: Luc Boudreau
Priority: Minor
The JCA MySQLValidConnectionChecker class has the driver name com.mysql.jdbc.Driver hard
coded which prevents it from using any other driver class provided by the standard MySQL
library. A good example of this is the replicated driver, which uses class
com.mysql.jdbc.ReplicationDriver.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira