[jbossts-issues] [JBoss JIRA] Commented: (JBTM-543) qa tests should support driver selection

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Tue May 5 14:31:46 EDT 2009


    [ https://jira.jboss.org/jira/browse/JBTM-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465855#action_12465855 ] 

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

        



More information about the jbossts-issues mailing list