[
https://issues.jboss.org/browse/JBTM-314?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson resolved JBTM-314.
--------------------------------
Assignee: Tom Jenkinson (was: Mark Little)
Resolution: Won't Fix
We have opened
https://issues.jboss.org/browse/JBTM-899 to resolve this issue in a more
contemporary manner
JDBCStore.getJDBCClass does not work for some JDBC drivers
----------------------------------------------------------
Key: JBTM-314
URL:
https://issues.jboss.org/browse/JBTM-314
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transaction Core
Reporter: Jeremy Stone
Assignee: Tom Jenkinson
Fix For: future
Implementation of com.arjuna.ats.internal.arjuna.objectstore.JDBCStore
getJDBCClass(Connection) breaks if JDBC driver DatabaseMetaData getDriverName() is not
consistent between driver releases or driver implementations (e.g. SQLServer), and tries
to load illegally named classes if first word of reported driver name contains illegal
characters (e.g. MySql).
Maybe a pluggable strategy for determination of the class should be used instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira