db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2047) TestDataSourceFactory doesn't work correctly outside the old harness
Date Mon, 06 Nov 2006 17:57:38 GMT
    [ http://issues.apache.org/jira/browse/DERBY-2047?page=comments#action_12447484 ] 
Knut Anders Hatlen commented on DERBY-2047:

Thanks Dan, I hadn't noticed your comment about this problem under DERBY-2043. Your approach
sounds cleaner to me. Feel free to take over the issue and continue as you had planned.

There is at least one problem with my patch. JDBCClient.getDataSourceClassName() doesn't return
the correct name for JSR169, so BaseJDBCTestCase.getConnection() won't work under JSR169.
Should be easy to fix, though. I think the changes I made to JDBCClient will be useful for
your approach too.

> TestDataSourceFactory doesn't work correctly outside the old harness
> --------------------------------------------------------------------
>                 Key: DERBY-2047
>                 URL: http://issues.apache.org/jira/browse/DERBY-2047
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>         Attachments: DataSource.java, derby-2047.diff, derby-2047.stat
> TestDataSourceFactory uses TestUtil to create DataSource, ConnectionPoolDataSource and
XADataSource objects. TestUtil needs to run in the old harness in order to detect which framework
it is running under, so it will create embedded data sources for all JUnit tests that are
run outside the old harness.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message