[
https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465328
]
Myrna van Lunteren commented on DERBY-2224:
-------------------------------------------
after the fix for DERBY-2228, parameterMapping no longer needs any changes.
Also, floattypes needs only 1 minor change.
re grantRevokeDDL - the stack trace showing the call java.math.BigDecimal with
wctme5.7(foundation) is documented in DERBY-1847.
With weme6.1 we get a little further; the create trigger statement actually
succeeds, but the insert fails:
--------
insert into t31TriggerTest values(1);
ERROR 38000: The exception 'java.lang.NoClassDefFoundError:
java.sql.DriverManager' was thrown while evaluating an expression.
ERROR XJ001: Java exception: 'java.sql.DriverManager:
java.lang.NoClassDefFoundError'.
--------
derby.log shows:
--------
ERROR 38000: The exception 'java.lang.NoClassDefFoundError:
java.sql.DriverManager' was thrown while evaluating an expression.
at
org.apache.derby.iapi.error.StandardException.newException(StandardException.java:309)
at
org.apache.derby.iapi.error.StandardException.unexpectedUserException(StandardException.java:558)
at
org.apache.derby.impl.services.reflect.DirectCall.invoke(ReflectGeneratedClass.java:164)
at
org.apache.derby.impl.sql.execute.RowResultSet.getNextRowCore(RowResultSet.java:151)
at
org.apache.derby.impl.sql.execute.OnceResultSet.getNextRowCore(OnceResultSet.java:177)
at
org.apache.derby.exe.ac2edd81ddx0110x2ca3x8055x0000576376c01d.g0(Unknown Source)
at
org.apache.derby.exe.ac2edd81ddx0110x2ca3x8055x0000576376c01d.execute(Unknown
Source)
at
org.apache.derby.impl.sql.GenericActivationHolder.execute(GenericActivationHolder.java:327)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:356)
at
org.apache.derby.impl.sql.execute.GenericTriggerExecutor.executeSPS(GenericTriggerExecutor.java:173)
at
org.apache.derby.impl.sql.execute.StatementTriggerExecutor.fireTrigger(StatementTriggerExecutor.java:80)
at
org.apache.derby.impl.sql.execute.TriggerEventActivator.notifyEvent(TriggerEventActivator.java:278)
at
org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(InsertResultSet.java:1120)
at
org.apache.derby.impl.sql.execute.InsertResultSet.open(InsertResultSet.java:494)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:358)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1182)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:585)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:517)
at org.apache.derby.impl.tools.ij.ij.executeImmediate(ij.java:321)
at org.apache.derby.impl.tools.ij.utilMain.doCatch(utilMain.java:517)
at
org.apache.derby.impl.tools.ij.utilMain.runScriptGuts(utilMain.java:370)
at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:268)
at org.apache.derby.impl.tools.ij.Main.go(Main.java:204)
at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:170)
at org.apache.derby.impl.tools.ij.Main.main(Main.java:72)
at org.apache.derby.tools.ij.main(ij.java:67)
============= begin nested exception, level (1) ===========
java.lang.NoClassDefFoundError: java.sql.DriverManager
at
org.apache.derbyTesting.functionTests.util.ProcedureTest.selectFromSpecificSchema(ProcedureTest.java:120)
at
org.apache.derby.exe.ac2edd81ddx0110x2ca3x8055x0000576376c01d.g2(Unknown Source)
at
org.apache.derby.exe.ac2edd81ddx0110x2ca3x8055x0000576376c01d.e1(Unknown Source)
at
org.apache.derby.impl.services.reflect.DirectCall.invoke(ReflectGeneratedClass.java:141)
at
org.apache.derby.impl.sql.execute.RowResultSet.getNextRowCore(RowResultSet.java:151)
at
org.apache.derby.impl.sql.execute.OnceResultSet.getNextRowCore(OnceResultSet.java:177)
at
org.apache.derby.exe.ac2edd81ddx0110x2ca3x8055x0000576376c01d.g0(Unknown Source)
at
org.apache.derby.exe.ac2edd81ddx0110x2ca3x8055x0000576376c01d.execute(Unknown
Source)
at
org.apache.derby.impl.sql.GenericActivationHolder.execute(GenericActivationHolder.java:327)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:356)
at
org.apache.derby.impl.sql.execute.GenericTriggerExecutor.executeSPS(GenericTriggerExecutor.java:173)
at
org.apache.derby.impl.sql.execute.StatementTriggerExecutor.fireTrigger(StatementTriggerExecutor.java:80)
at
org.apache.derby.impl.sql.execute.TriggerEventActivator.notifyEvent(TriggerEventActivator.java:278)
at
org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(InsertResultSet.java:1120)
at
org.apache.derby.impl.sql.execute.InsertResultSet.open(InsertResultSet.java:494)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:358)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1182)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:585)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:517)
at org.apache.derby.impl.tools.ij.ij.executeImmediate(ij.java:321)
at org.apache.derby.impl.tools.ij.utilMain.doCatch(utilMain.java:517)
at
org.apache.derby.impl.tools.ij.utilMain.runScriptGuts(utilMain.java:370)
at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:268)
at org.apache.derby.impl.tools.ij.Main.go(Main.java:204)
at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:170)
at org.apache.derby.impl.tools.ij.Main.main(Main.java:72)
at org.apache.derby.tools.ij.main(ij.java:67)
============= end nested exception, level (1) ===========
I will accept the differences in these 3 tests, as well as timestampArith (see
DERBY-2225), and make a new patch, but I'm still checking to see if I can
figure out what's wrong with I18NImportExport.java.
> Test harness should support J2ME 1.1
> ------------------------------------
>
> Key: DERBY-2224
> URL: https://issues.apache.org/jira/browse/DERBY-2224
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.2.0, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY_2224_harness.diff, DERBY_2224_tests.diff
>
>
> I would like to enable the 'old' test harness to support the new version of
> IBM's j2ME implementation, which is based on j2ME jdk spec version 1.1. This
> is available with a product named Websphere Everyplace Micro Edition 6.1.
> from IBM.
> We already support j9_foundation, which matches to j2ME jdk spec 1.0. I'd
> like to add j9_foundation11, which then matches to j2ME jdk spec 1.1.
> I'm proposing to switch my automated tests over to the newer version going
> forward, and to minimize complexity of the change, I'd like to make the
> canons reflect behavior of the new version. The differences are minimal.
> However, I want to be able to still run with the old (except where the
> results differ, failures would occur with the old version).
> One of the reasons for moving to the new version is that there is a bug with
> the older version in regards to security manager, preventing a smooth run of
> the junit tests, and I'd like to run all short-running tests (suites.All and
> derbyall) with at least one of the versions. Another reason is that the j2ME
> spec 1.0 is really old.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
