[jboss-jira] [JBoss JIRA] Closed: (JBAS-5035) MySQLValidConnectionChecker has driver name com.mysql.jdbc.Driver hard coded
[ http://jira.jboss.com/jira/browse/JBAS-5035?page=all ]
Adrian Brock closed JBAS-5035.
------------------------------
Fix Version/s: JBossAS-5.0.0.Beta3
JBossAS-4.2.3.GA
Resolution: Done
Much better thanks. I've added you to our copyright.txt :-)
I changed the name to MySQLReplicationValidConnectionChecker since that makes more sense.
I also raised a subtask to fix the other checkers that are caching Methods.
When I fix those, I'll also optimize yours so it does cache the Method but as a
transient field
and re-initializes the reference in a readObject() method.
Getting the method on every invocation can be slow.
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.0.5.GA, JBossAS-4.2.0.GA
Environment: Any
Reporter: Luc Boudreau
Assigned To: Adrian Brock
Priority: Minor
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
Attachments: MySQLValidReplicationConnectionChecker.java
Time Spent: 1 hour
Remaining Estimate: 0 minutes
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