[
https://issues.apache.org/jira/browse/DERBY-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-5374:
--------------------------------------
Attachment: DERBY-5374.diff
With weme 6.2 (j2ME/Foundation), with the following in ijTest5:
if (JDBC.vmSupportsJSR169()) {
props.setProperty("ij.dataSource",
"org.apache.derby.jdbc.EmbeddedSimpleDataSource");
props.setProperty("ij.dataSource.databaseName", "wombat");
props.setProperty("ij.dataSource.createDatabase", "create");
}
I get a diff with weme 6.2 if all three lines are there, because the database
was already created. With showNoConnectionsAtStartup=true this gets masked...
If I comment out the createDatabase property line, I get a diff because of an
extra connection (i.e. it shows Connection0 and Connection1. This is because of
the CleanDatabase Setup).
If I comment out also the ij.dataSource.databaseName line, I get an extra line
with error message 'XJ004: Database ' ' not found.
And if I don't set ij.dataSource at all, we get the getURL(String) method not
found error.
In all, I don't think this test can be made to work exactly the same with j2ME
as with the more richer jvms.
In the old harness we handled this sort of difference by adding another master
file, but although it would've made the test work, maintaining multiple masters
is a nightmare, and as this test never ran with JSR169/j2ME/Foundation, and
it's not testing major functionality, but only one test case, I think it's ok
to not run this with JSR169/j2ME/Foundation.
So I'm attaching a patch that I will commit shortly, which skips this test from
running with JSR169, both in the test itself and in the tools._Suite.
In addition, I noticed the .sql file still mentions ConnOne, which was removed,
so I changed that to say Connection0.
> converted ij5Test fails with weme6.2 (CDC/Foundation):
> junit.framework.ComparisonFailure: Output at line 1 expected:<CONNECTION0* -
> jdbc:derby:wombat> but was:<ERROR XJ004: Database '' not found.>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5374
> URL: https://issues.apache.org/jira/browse/DERBY-5374
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.9.0.0
> Environment: windows XP, with weme6.2 (IBM's CDC/Foundation
> implementation)
> Reporter: Myrna van Lunteren
> Attachments: DERBY-5374.diff
>
>
> The newly converted (to junit) test ij5Test fails with weme 6.2:
> ij5(org.apache.derbyTesting.functionTests.tests.tools.ij5Test)junit.framework.ComparisonFailure:
> Output at line 1 expected:<CONNECTION0* - jdbc:derby:wombat> but
> was:<ERROR XJ004: Database '' not found.>
> at
> junit.framework.AssertionFailedError.<init>(AssertionFailedError.java:11)
> at junit.framework.ComparisonFailure.<init>(ComparisonFailure.java:19)
> at
> org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon(CanonTestCase.java:109)
> at
> org.apache.derbyTesting.functionTests.util.ScriptTestCase.runTest(ScriptTestCase.java:204)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:112)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at
> org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> This is likely a similar problem as described in DERBY-5373 (re
> importExportIJ).
> see also (until cleaned up at some point in the future):
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.2/1152992-suites.All_diff.txt
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
