[ http://issues.apache.org/jira/browse/DERBY-2047?page=all ]
Daniel John Debrunner updated DERBY-2047:
-----------------------------------------
Attachment: DataSource.java
I was also working on this issue under DERBY-2043 taking a slightly different
approach and not getting as far as Knut.
I was moving the DataSource methods over to the jutil package as this is very
much part of that package and extends beyond functional tests.
The other differences in approach were driving the data source bean properties
from the TestConfiguration and using a HashMap to define the data source
properties, not a Properites object. This then allowed the caller to specifiy
the type of the bean by passing an object of the correct type, rather than
having the bean types hard coded at the low level generic code.
Attached is a DataSource class, very much a work in progress and untested, e.g.
null is passed for the data source name as I hadn't got around to setting it,
just wanted the code to compile.
> 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: 10.3.0.0
> 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
