Bug 1019186 - allow a datasource class name to be used instead of forcing the use of the driver class
allow a datasource class name to be used instead of forcing the use of the dr...
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JCA (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: EAP 6.4.0
Assigned To: Tom Fonteyne
Martin Simka
Depends On:
  Show dependency treegraph
Reported: 2013-10-15 05:22 EDT by Tom Fonteyne
Modified: 2017-10-09 20:08 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 955648
Last Closed: 2014-09-03 07:39:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker JBJCA-1023 Major Closed Use datasource class as default 2014-09-03 07:53:32 EDT

  None (edit)
Comment 1 Tom Fonteyne 2013-10-15 06:11:12 EDT
[tom@orac Branch_1_0]$ svn ci adapters/src/main/java/org/jboss/jca/adapters/jdbc/local/LocalManagedConnectionFactory.java -m "[bz-1019186] allow the use of a datasource class when set instead of always using the hardcoded driver class"
Sending        adapters/src/main/java/org/jboss/jca/adapters/jdbc/local/LocalManagedConnectionFactory.java
Transmitting file data.                                                          
Committed revision 114533.
Comment 2 Tom Fonteyne 2013-10-15 06:16:25 EDT
Example setup:

  <datasource jndi-name="java:jboss/datasources/oracleDS" pool-name="oracleDS" enabled="true" use-ccm="true" use-java-context="true" >
  <connection-url>     jdbc:oracle:thin:@oracleserver.redhat.com:1521:oracle</connection-url>
  <connection-property name="URL">jdbc:oracle:thin:@oracleserver.redhat.com:1521:oracle</connection-property>
    <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
  <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
  <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
    <driver name="oracle" module="com.oracle.jdbc">

Note the presence of both:
  connection-url: needed for JBoss
  connection-property name="URL"> : needed for the Oracle driver
Their setting should be identical
Comment 3 Martin Simka 2013-12-06 06:49:31 EST
This fix is not in EAP 6.2.0.CR3/GA.
Comment 4 tom.jenkinson 2014-09-03 07:15:45 EDT
Hi guys,

This issue is quite old, is it still required or can it be dropped?

Comment 5 Martin Simka 2014-09-03 07:25:51 EDT
I think it's 6.4.0 RFE https://issues.jboss.org/browse/EAP6-151
Comment 6 tom.jenkinson 2014-09-03 07:36:05 EDT
Thanks Martin, so I guess that means we can close the BZ as its being tracked as an requirement in Jira?
Comment 7 Martin Simka 2014-09-03 07:39:09 EDT
I think so, closing

6.4.0 RFE tracked in https://issues.jboss.org/browse/EAP6-151

Note You need to log in before you can comment on or make changes to this bug.