[ http://issues.apache.org/jira/browse/DERBY-949?page=comments#action_12370108 ]
Myrna van Lunteren commented on DERBY-949: ------------------------------------------ The patch DERBY-949_2006_03_11.* fixes this issue. I ran derbyall with j2ME (wctme5.7_foundation) and jdk142 and encountered no new failures. (jdk142 - wisconsin, j9 - grantRevoke, bootLock). Note that with this patch I did modify TestUtil.getConnection() so it worked in all cases tested. I think this would be good place to have a generic getConnection method, but currently, it does not provide a connection to networkserver. I will work on that in a next patch - the tests listed in this bug do not currently run with networkserver and I tried to keep the changes specific to this issue. > Clean up tests to use common method to get connections > ------------------------------------------------------ > > Key: DERBY-949 > URL: http://issues.apache.org/jira/browse/DERBY-949 > Project: Derby > Type: Test > Components: Test > Versions: 10.2.0.0 > Reporter: Deepa Remesh > Assignee: Myrna van Lunteren > Priority: Minor > Fix For: 10.2.0.0 > Attachments: DERBY-949_2006_03_11.diff, DERBY-949_2006_03_11.stat > > Currently some tests have code to check the environment and get connection > using DriverManager/DataSource. This logic has been moved to > TestUtil.getConnection method. Cleanup tests to use this method. List of > tests: > store/TestDurabilityProperty.java > store/backupRestore1.java > store/OnlineBackup tests > lang/logStream.java > lang/closed.java > Also, add comment to ij.startJBMS method mentioning TestUtil.getConnection > method. See https://issues.apache.org/jira/browse/DERBY-907#action_12365954 -- 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
