[
https://issues.jboss.org/browse/JBJCA-637?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JBJCA-637:
-----------------------------------------------
Tom Fonteyne <tfonteyn(a)redhat.com> made a comment on [bug
957175|https://bugzilla.redhat.com/show_bug.cgi?id=957175]
@John Doyle: "if a datasource class is defined first, then fallback to
java.sql.Driver - the opposite of today."
This bit is incorrect: "the opposite of today."
The situation "today" is that the datasource class can *never* be used in EAP
for the simple fact that all major vendors driver have the driver class preset.
@Jesper Pedersen: "
The "datasource-class" element is there in order to support JDBC like drivers
which doesn't implement the java.sql.Driver class."
Could you please provide an example ? I mean do you have such a non-driver that can be
deployed to EAP so we can see the functionality working as you state ?
DataSource support
------------------
Key: JBJCA-637
URL:
https://issues.jboss.org/browse/JBJCA-637
Project: IronJacamar
Issue Type: Task
Components: Common, Deployer, JDBC
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Fix For: 1.0.2.Final, 1.1.0.Alpha1
We should support <datasource> deployments based on a javax.sql.DataSource
instance.
Add <datasource-class> to <datasource> and <driver> as optional.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira