You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/01/09 18:28:27 UTC
[jira] Created: (DERBY-2224) Test harness should support J2ME 1.1
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
Priority: Minor
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
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465331 ]
Myrna van Lunteren commented on DERBY-2224:
-------------------------------------------
re I18NImportExport.java: the stack trace with weme6.1 is like so:
---------------
JAVA ERROR: java.lang.NoSuchMethodError: java/sql/ResultSet.getBigDecimal(II)Ljava/math/BigDecimal;
java.lang.NoSuchMethodError: java/sql/ResultSet.getBigDecimal(II)Ljava/math/BigDecimal;
at org.apache.derby.iapi.tools.i18n.LocalizedResource.getLocalizedString(LocalizedResource.java:335)
at org.apache.derby.tools.JDBCDisplayUtil.DisplayRow(JDBCDisplayUtil.java:627)
at org.apache.derby.tools.JDBCDisplayUtil.indent_DisplayResults(JDBCDisplayUtil.java:338)
at org.apache.derby.tools.JDBCDisplayUtil.indent_DisplayResults(JDBCDisplayUtil.java:239)
at org.apache.derby.tools.JDBCDisplayUtil.DisplayResults(JDBCDisplayUtil.java:227)
at org.apache.derby.impl.tools.ij.utilMain.displayResult(utilMain.java:457)
at org.apache.derby.impl.tools.ij.utilMain.doCatch(utilMain.java:520)
at org.apache.derby.impl.tools.ij.utilMain.runScriptGuts(utilMain.java:373)
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)
--------------
> 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
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465281 ]
Myrna van Lunteren commented on DERBY-2224:
-------------------------------------------
committed the test harness changes (not the canons/test changes) with http://svn.apache.org/viewvc?view=rev&revision=496847
> 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
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463595 ]
Daniel John Debrunner commented on DERBY-2224:
----------------------------------------------
Can you explain the changes in parameterMapping that seem to indicate that ResultSet.getBigDecimal was successfully called, when in fact no such method exists in JSR169. Here's one example.
- setNull with batching support(SMALLINT) IC
+ setNull with batching support(SMALLINT) getBigDecimal=null was null true
There are also interesting changes in grantRevokeDDL.out, e.g. this statement succeeds when it failed with the previous version of j9.
ij(MAMTA3)> -- following will pass because all the required privileges are in place for mamta3
create trigger tr31t31 after insert on t31TriggerTest for each statement
insert into mamta1.t13TriggerTest values (values mamta1.selectFromSpecificSchema(1));
-ERROR: Failed with SQLSTATE XJ001
+0 rows inserted/updated/deleted
I don't understand the change in parameterMapping.java, I would have thought only the way the test determines if BigDecimal is fully supported (in the VM and the JDBC api) would change, but instead there are extra if conditions in the running of the test. Should this test use the utility method you modified in util/BigDecimalHandler.java?
Any idea why we need a j9 foundation specific master file for I18NImportExport.out?
> 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
[jira] Updated: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2224:
--------------------------------------
Attachment: DERBY-2224_tests_20070118.diff
> 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_tests_20070116.diff, DERBY-2224_tests_20070116.stat, DERBY-2224_tests_20070118.diff, 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
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467171 ]
Myrna van Lunteren commented on DERBY-2224:
-------------------------------------------
Modified the java/testing/README.htm to reflect use of 6.1.1 instead of wctme5.7 with revision 499590.
> 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
> Fix For: 10.3.0.0
>
> Attachments: DERBY-2224_tests_20070116.diff, DERBY-2224_tests_20070116.stat, DERBY-2224_tests_20070118.diff, 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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
[jira] Assigned: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reassigned DERBY-2224:
-----------------------------------------
Assignee: Myrna van Lunteren
> 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
>
> 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
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465336 ]
Myrna van Lunteren commented on DERBY-2224:
-------------------------------------------
added a patch that:
- modifies org.apache.derby,iapi.tools.i18n.LocalizedResource to check for the ability to call ResultSet.getBigDecimal
- updates master-canons with output with weme 6.1 for the following tests:
- lang/grantRevokeDDL.sql
- lang/floattypes.sql
- lang/timestampArith.sql
- changes the method org.apache.derby.tools.functionTests.util.BigDecimalHandler to check for ability to call ResultSet.getBigDecimal.
If there are no further comments, I'd like to commit this...
> 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_tests_20070116.diff, DERBY-2224_tests_20070116.stat, 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
[jira] Updated: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2224:
--------------------------------------
Attachment: DERBY_2224_harness.diff
> 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
>
>
> 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
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465887 ]
Myrna van Lunteren commented on DERBY-2224:
-------------------------------------------
I added some comments in those two classes, I hope it makes things clearer?
> 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_tests_20070116.diff, DERBY-2224_tests_20070116.stat, DERBY-2224_tests_20070118.diff, 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
[jira] Updated: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2224:
--------------------------------------
Attachment: (was: DERBY_2224_harness.diff)
> 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
>
> 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
[jira] Updated: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2224:
--------------------------------------
Attachment: DERBY_2224_harness.diff
> 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
>
> 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
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463743 ]
Daniel John Debrunner commented on DERBY-2224:
----------------------------------------------
I think these are symtoms of the fact that Foundation 1.1 introduces BigDecimal but the Derby code is not set up to handle it correctly with JSR 169.
Derby's JSR 169 support (which does not have the set/getBigDecimal methods) was written against Foundation 1.0 which does not have BigDecimal and thus makes that assumption. So a combination of JSR169 and BigDecimal was not anticipated. I'll add some notes to DERBY-2210 and enter a new bug.
> 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
[jira] Updated: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2224:
--------------------------------------
Attachment: DERBY_2224_tests.diff
> 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
[jira] Updated: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2224:
--------------------------------------
Derby Info: [Patch Available]
I added patches for trunk for the harness and a few tests. It appears that this version of the j9 jvm includes a java.math.BigDecimal, but the jdbc support has not been upgraded to include methods like ResultSet.getBigDecimal and the like, which results in a few test failures, and for which I had to modify the util/BigDecimalHandler.java.
I'm checking into whether or not this is intentional, but in the mean time, I think the patches can stand as they are.
I'll leave this for review for a day, and plan to commit on Thursday.
> 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
[jira] Closed: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-2224.
-------------------------------------
> 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
> Fix For: 10.3.0.0
>
> Attachments: DERBY-2224_tests_20070116.diff, DERBY-2224_tests_20070116.stat, DERBY-2224_tests_20070118.diff, 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
[jira] Resolved: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-2224.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
committed change 497678, see: http://svn.apache.org/viewvc?view=rev&revision=497678
commit comment:
DERBY-2224 - update j9_foundation master/canons to weme 6.1 (J2ME 1.1) results
- this change includes a change to ij because java.math.BigDecimal
is now available, but JSR169 does not support methods like
ResultSet.getBigDecimal(...).
- this change also accepts incorrect behavior in timestampArith.java, which is
covered in DERBY-2225.
> 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
> Fix For: 10.3.0.0
>
> Attachments: DERBY-2224_tests_20070116.diff, DERBY-2224_tests_20070116.stat, DERBY-2224_tests_20070118.diff, 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
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463641 ]
Myrna van Lunteren commented on DERBY-2224:
-------------------------------------------
Thx for the review!
re I18NImportExport.sql - the .tmp file shows why there is different behavior:
....
ij> LOCALIZEDDISPLAY ON;
ij> select * from tab1;
C1 |C2 |C3
-----------------------------------------------
JAVA ERROR: java.lang.NoSuchMethodError: java/sql/ResultSet.getBigDecimal(II)Ljava/math/BigDecimal;
...
(twice).
re parameterMapping.java - the test does use the BigDecimalHandler utility already, however, it ran into this:
---------
....
For setXXX() methods that pass an object, a null and valid values are checked
setByte() getBigDecimal=98.00000 was null false JDBC MATCH(OK)
setByte() as batch java.lang.NoSuchMethodError: java/sql/PreparedStatement.setBigDecimal(ILjava/math/BigDecimal;)V
at org.apache.derby.iapi.types.SQLDecimal.setInto(SQLDecimal.java:600)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeBatchElement(EmbedPreparedStatement.java:1007)
at org.apache.derby.impl.jdbc.EmbedStatement.executeBatch(EmbedStatement.java:924)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.parameterMapping.setXXX(parameterMapping.java:1197)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.parameterMapping.main(parameterMapping.java:459)
-------------
So, the engine code calls some set/getBigDecimal methods.
re grantRevokeDDL.sql:
A while ago I created the original master-canon for j9_foundation because of the failure, because (as was pointed out to me) triggers are not supported with CDC/JSR169/j2ME, according to the documentation. I concluded at the time (based on stack traces and watching the debugger) that this was because the engine code for triggers uses a BigDecimal call (somewhere. If you want details, I can backtrack, but it would take some time). Now that there is a java.math.BigDecimal, apparently, that piece of code passes; and so it fails a little further in the test.
In short, I was trying to get the tests to run cleanly even though there is really a bit of an engine issue here.
> 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
[jira] Updated: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2224:
--------------------------------------
Attachment: DERBY-2224_tests_20070116.diff
DERBY-2224_tests_20070116.stat
> 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_tests_20070116.diff, DERBY-2224_tests_20070116.stat, 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
[jira] Commented: (DERBY-2224) Test harness should support J2ME 1.1
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465880 ]
Daniel John Debrunner commented on DERBY-2224:
----------------------------------------------
I think the changes to LocalizedResource and BigDecimalHandler could use some comments indicating why the check is needed and why it's done that way. The class comment in BigDecimalHandler could be updated to reflect the new check. And with the check in BigDecimalHandler I don't think you can get a ClassNotFOundError anymore.
Also I never knew one could use the .class construct on primitives, such as 'int.class', I'd always used Integer.TYPE. Useful to know, thanks!
> 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_tests_20070116.diff, DERBY-2224_tests_20070116.stat, 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