2:08 p.m.
qa tests should support driver selection
----------------------------------------
Key: JBTM-543
URL: https://jira.jboss.org/jira/browse/JBTM-543
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.6.1
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.7.0
For some database servers we want to runs tests with multiple different versions of the
drivers. This is non-trivial, as the driver versions each use the same classnames, so only
one version can be on the classpath at a time. We'll need some kind of config
mechanism to alter the classpath on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:40 p.m.
New subject: [JBoss JIRA] Commented: (JBTM-543) qa tests should support driver selection
[
https://jira.jboss.org/jira/browse/JBTM-543?page=com.atlassian.jira.plugi...
]
Jonathan Halliday commented on JBTM-543:
----------------------------------------
There are a couple of different approaches to this.
The 'DTF' style one is to define multiple classpaths in the product config file
(JBossTS_JTS_JacORB_QA.xml) then have multiple node configurations, each referencing a
different classpath. Finally a set of different nodeconfig.xml files, each referencing a
different 'os' name i.e. node config / classpath. That's a log of extra xml as
the number of db drivers grows.
The second approach is to construct a default classpath containing a generic
'dbdriver.jar' entry but no other db drivers (unlike now where all the drivers are
on the classpath, although at most one version of each), then use the run-dtf-local.xml
file to copy the desired driver from a holding dir to 'dbdriver.jar' for each set
of tests. This becomes a pain the next when a driver has more than one .jar though. Maybe
use a dir rather than a .jar, as the config is reloaded for each test group and will
rescan the dir at that time anyhow.
qa tests should support driver selection
----------------------------------------
Key: JBTM-543
URL: https://jira.jboss.org/jira/browse/JBTM-543
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 4.6.1
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.7.0
For some database servers we want to runs tests with multiple different versions of the
drivers. This is non-trivial, as the driver versions each use the same classnames, so only
one version can be on the classpath at a time. We'll need some kind of config
mechanism to alter the classpath on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:31 p.m.
New subject: [JBoss JIRA] Commented: (JBTM-543) qa tests should support driver selection
[
https://jira.jboss.org/jira/browse/JBTM-543?page=com.atlassian.jira.plugi...
]
Jonathan Halliday commented on JBTM-543:
----------------------------------------
Decided to go for the second approach. Only problem is that the JNDIManager links against
the drivers for all supported dbs, whilst under the new regime only one at a time is in
the runtime classpath, so it won't classload at runtime. Fixed that by changing it to
use reflection for configuration of the XADataSource bean properties, which has the added
bonus of meaning we only need the db drivers for running tests, not building them.
Fixed the classpath so it includes a <jar
name="$(PRODUCT.DIR)/qa/lib/selected_dbdriver/*.jar"/> entry and changed the
build so it parks all the possible drivers in /qa/lib/all_dbdrivers/ Linked those bits
together with a update for run-dtf-local.xml so that it copies the drivers needed for each
db test set from all_dbdrivers to selected_driver. Now it should be possible to edit
run-dtf-local.xml to select the desired driver based on some property e.g. the java
runtime version jdbc3 vs. jdbc4 drivers.
qa tests should support driver selection
----------------------------------------
Key: JBTM-543
URL: https://jira.jboss.org/jira/browse/JBTM-543
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 4.6.1
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.7.0
For some database servers we want to runs tests with multiple different versions of the
drivers. This is non-trivial, as the driver versions each use the same classnames, so only
one version can be on the classpath at a time. We'll need some kind of config
mechanism to alter the classpath on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:25 p.m.
New subject: [JBoss JIRA] Closed: (JBTM-543) qa tests should support driver selection
[
https://jira.jboss.org/jira/browse/JBTM-543?page=com.atlassian.jira.plugi...
]
Jonathan Halliday closed JBTM-543.
----------------------------------
Resolution: Done
qa tests should support driver selection
----------------------------------------
Key: JBTM-543
URL: https://jira.jboss.org/jira/browse/JBTM-543
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 4.6.1
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.7.0
For some database servers we want to runs tests with multiple different versions of the
drivers. This is non-trivial, as the driver versions each use the same classnames, so only
one version can be on the classpath at a time. We'll need some kind of config
mechanism to alter the classpath on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:23 p.m.
New subject: [JBoss JIRA] Reopened: (JBTM-543) qa tests should support driver selection
[
https://jira.jboss.org/jira/browse/JBTM-543?page=com.atlassian.jira.plugi...
]
Jonathan Halliday reopened JBTM-543:
------------------------------------
qa tests should support driver selection
----------------------------------------
Key: JBTM-543
URL: https://jira.jboss.org/jira/browse/JBTM-543
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 4.6.1
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.6.1.CP01, 4.7.0
For some database servers we want to runs tests with multiple different versions of the
drivers. This is non-trivial, as the driver versions each use the same classnames, so only
one version can be on the classpath at a time. We'll need some kind of config
mechanism to alter the classpath on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:23 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-543) qa tests should support driver selection
[
https://jira.jboss.org/jira/browse/JBTM-543?page=com.atlassian.jira.plugi...
]
Jonathan Halliday updated JBTM-543:
-----------------------------------
Fix Version/s: 4.6.1.CP01
qa tests should support driver selection
----------------------------------------
Key: JBTM-543
URL: https://jira.jboss.org/jira/browse/JBTM-543
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 4.6.1
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.6.1.CP01, 4.7.0
For some database servers we want to runs tests with multiple different versions of the
drivers. This is non-trivial, as the driver versions each use the same classnames, so only
one version can be on the classpath at a time. We'll need some kind of config
mechanism to alter the classpath on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:41 p.m.
New subject: [JBoss JIRA] Closed: (JBTM-543) qa tests should support driver selection
[
https://jira.jboss.org/jira/browse/JBTM-543?page=com.atlassian.jira.plugi...
]
Jonathan Halliday closed JBTM-543.
----------------------------------
Resolution: Done
qa tests should support driver selection
----------------------------------------
Key: JBTM-543
URL: https://jira.jboss.org/jira/browse/JBTM-543
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 4.6.1
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.6.1.CP01, 4.7.0
For some database servers we want to runs tests with multiple different versions of the
drivers. This is non-trivial, as the driver versions each use the same classnames, so only
one version can be on the classpath at a time. We'll need some kind of config
mechanism to alter the classpath on the fly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5682
days inactive
5776
days old
jbossts-issues@lists.jboss.org
6 comments
1 participants
participants (1)
-
Jonathan Halliday (JIRA)