db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-398) Exclude tests for J2ME/CDC/Foundation platform
Date Fri, 27 Jan 2006 03:12:35 GMT
    [ http://issues.apache.org/jira/browse/DERBY-398?page=comments#action_12364173 ] 

Kathey Marsden commented on DERBY-398:

I checked in this parameterMapping_2.diff

Date: Thu Jan 26 19:06:10 2006
New Revision: 372708

URL: http://svn.apache.org/viewcvs?rev=372708&view=rev

Thanks for getting these tests running with J2ME.

I think in that in the future we can probably do more with parameterMapping to eliminate some
of the J2ME specific branches.  One thought is instead of  having a totally separate initialization
for  B3_GET_OBJECT, you could have just a separate class.
    decimalClass = java.math.BigDecimal.class;
   decimalClass = java.lang.String.class;

Then just have a single initialization of  B3_GET_OBJECT 

> Exclude tests for J2ME/CDC/Foundation platform
> ----------------------------------------------
>          Key: DERBY-398
>          URL: http://issues.apache.org/jira/browse/DERBY-398
>      Project: Derby
>         Type: Sub-task
>   Components: Test
>     Reporter: Deepa Remesh
>     Assignee: Deepa Remesh
>  Attachments: derby-398_2.diff, derby-398_2.status, derbyall_report_2.txt, jdbcapi_lang_patch.diff,
jdbcapi_lang_patch.status, jdk14_tests_3.diff, jdk14_tests_3.status, nullSQLText_patch.diff,
nullSQLText_patch.status, parameterMapping_2.diff, parameterMapping_2.status, readme_patch.diff,
store_patch.diff, store_patch.status, wisc_rename_patch.diff, wisc_rename_patch.status, wisconsin_patch.diff,
> Exclude tests which use DriverManager, Driver or BigDecimal classes which are not in
J2ME or JSR169. Ensure that derbyall can be run successfully in J2ME/CDC/Foundation platform
using the JDBC Optional Package for CDC/Foundation Profile (JSR169).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message