[ http://issues.apache.org/jira/browse/DERBY-453?page=comments#action_12323072 ]
Deepa Remesh commented on DERBY-453: ------------------------------------ In that case, I will change to setString. But I am little confused as to how I should proceed. I see two ways to handle the test: 1. In callSetObject in outparams.java, I can continue to pass "666.666" to setBigDecimalString. This will give error in setString for short primitive type because the String passed is not convertible to short. This is the expected behaviour. I can update the master file for j9_foundation accordingly. 2. I can pass "666" to setBigDecimalString. This will work with all the object types for which conversion is valid. But we are not testing a decimal value. Please let me know which of these is a good approach or if there is another way of doing this. > Create a test wrapper to run tests using BigDecimal in J2ME/CDC/Foundation > -------------------------------------------------------------------------- > > Key: DERBY-453 > URL: http://issues.apache.org/jira/browse/DERBY-453 > Project: Derby > Type: Improvement > Components: Test > Environment: J2ME/CDC/Foundation using IBM's WCTME 5.7 > Reporter: Deepa Remesh > Assignee: Deepa Remesh > Priority: Minor > Attachments: derby-453.diff, derby-453.status, > derby_453_outparams_patch1.diff, derby_453_outparams_patch1.status, > derby_453_outparams_patch2.diff > > The following tests are currently excluded in J2ME/CDC/Foundation because > they use BigDecimal class. > I18NImportExport > batchUpdate > LOBTest > parameterMapping > resultset > StmtCloseFunTest > cast > functions > outparams > procedure > triggerRefClause > wisconsin > iepnegativetests > ieptests > importExportThruIJ > importExport > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
