The following tests are currently excluded in J2ME/CDC/Foundation because they use BigDecimal class.
To run the above tests in this environment, test utility classes have to be written so that the methods using BigDecimal are redirected depending on the VM environment. The initial goal is to submit a patch for the test resultset.java. After this, sub-tasks will be opened if changes are needed to run the other tests.
|Workflow||jira [ 12322142 ]||Default workflow, editable Closed status [ 12797575 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Fix Version/s||10.2.0.0 [ 11187 ]|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
[ I spoke with Deepa off-line about this and had a few comments on the patch.
I think the wrapper function for getBigDecimal by columnname,canConvertToDecimal, should take a columnname parameter rather than getting it in the method just for the sake of clarity in the tests.
I think it would be good to have a class comment with the summary of the handling of BigDemcimal values in J2ME and an explanation of how tests that use BigDecimal values should be written so that they work with J2ME.
I am not really comfortable with the mock up of data conversion exceptions for J2ME but don't really have a better idea #:).
Need to check the types listed in canConvertToDecimal. I think some of them are not quite right.
|Field||Original Value||New Value|
|Assignee||Deepa Remesh [ deepa ]|