Bug 1097166

Summary:	Cannot deploy the latest MySQL driver into EAP
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	tom.jenkinson
Component:	JCA	Assignee:	Enrique Gonzalez Martinez <egonzale>
Status:	CLOSED NOTABUG	QA Contact:	Martin Simka <msimka>
Severity:	urgent	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.3.0	CC:	egonzale, hhovsepy, msimka, ochaloup, smaestri, smumford, tom.jenkinson
Target Milestone:	---	Keywords:	Reopened
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1027126	Environment:
Last Closed:	2015-11-27 11:38:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1027126
Bug Blocks:

Comment 1 Ondrej Chaloupka 2014-06-10 06:30:37 UTC

In case could not be somelike connected with this issue?
https://bugzilla.redhat.com/show_bug.cgi?id=1107120

Comment 2 tom.jenkinson 2014-06-10 10:03:51 UTC

Hi,

To be clear this is just about deploying the latest version of the MySQL driver into the AS.

Basically, pop the driver into the deployments folder and it didn't work.

It looks like an OSGi issue so not really sure if its JCA but its certainly not TM.

Tom

Comment 3 Jesper Pedersen 2014-06-10 11:49:14 UTC

Override using the <driver-class> element in <driver>

Comment 9 JBoss JIRA Server 2014-09-15 12:49:39 UTC

Tom Jenkinson <tom.jenkinson> updated the status of jira JBTM-2121 to Closed

Comment 10 Martin Simka 2014-11-14 11:50:17 UTC

reopen

we should at least consider using first driver in services/java.sql.Driver as default

Current behavior confuses a lot of users. 

First class is already used when driver is in module and data-source class isn't specified while adding driver. See. https://bugzilla.redhat.com/show_bug.cgi?id=1107120

Comment 15 Enrique Gonzalez Martinez 2015-11-27 11:38:33 UTC

Giving a second thought about this. 

Doing this way (comment #11) would cause problems in case of upgrading jdbc drivers (this bz is an example).

If we use one driver by default (arbitrary policy about picking one of the listed in the jar file), we are making this problem not visible. This could cause a problem (possible use of the wrong driver, not supported, not tested, etc...). I think is better to leave the behaviour as it is. It seems consistent to me.