Issue Details (XML | Word | Printable)

Key: DERBY-470
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Deepa Remesh
Reporter: Deepa Remesh
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Derby

Exception when using LOCALIZEDDISPLAY with JSR169

Created: 26/Jul/05 03:55 AM   Updated: 30/Sep/05 02:25 AM
Return to search
Component/s: Localization
Affects Version/s: None
Fix Version/s: 10.1.2.1, 10.2.1.6

Time Tracking:
Issue & Sub-Tasks
Issue Only
Not Specified

File Attachments:
  Size
File Licensed for inclusion in ASF works derby-470.diff 2005-07-28 02:23 AM Deepa Remesh 2 kB
File Licensed for inclusion in ASF works derby-470.status 2005-07-28 02:23 AM Deepa Remesh 0.2 kB
Environment: IBM's J2ME/CDC/Foundation Profile and JSR169

Resolution Date: 30/Sep/05 02:25 AM

Sub-Tasks  All   Open   
No sub-tasks match this view.

 Description  « Hide
As I did not get any response to my mail, I am opening a JIRA issue for this.

When I run the test i18n/I18NImportExport.java with JSR169 using IBM's J2ME/CDC/Foundation Profile, I get the following exception:
"JAVA ERROR: java.lang.NoSuchMethodError: java/sql/ResultSet.getBigDecimal(II)Ljava/math/BigDecimal;"

In the test, LOCALIZEDDISPLAY is on and the table has a DECIMAL column. This causes the exception. On looking at the code, following is done to format DECIMAL types in LocalizedResource:

if (type == Types.NUMERIC || type == Types.DECIMAL) {
      return getNumberAsString(rs.getBigDecimal(columnNumber, rsm.getScale(columnNumber)));
}

where getNumberAsString method does the following:

public String getNumberAsString(Object o){
      if (enableLocalized){
            return formatNumber.format(o, new StringBuffer(), new FieldPosition(0)).toString();
      }
      else {
            return o.toString();
      }
 }

As a solution, I am planning to do the following:
1. Check for BigDecimal class in the JVM by doing a Class.forName
2. Call getNumberAsString for NUMERIC and DECIMAL types only if BigDecimal class is available. Otherwise, return rs.getString.

This solution would mean that NUMERIC and DECIMAL types will not be localized in these JVM environments. Please let me know if any comments on this.

Thanks,
Deepa



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Repository Revision Date User Message
ASF #239718 Wed Aug 24 17:41:29 UTC 2005 kmarsden DERBY-470 - Exception when using LOCALIZEDDISPLAY with JSR169

1. Check for BigDecimal class in the JVM by doing a Class.forName
2. Call getNumberAsString for NUMERIC and DECIMAL types only if BigDecimal class is available. Otherwise, return rs.getString.

Contributed by Deepa Remesh
Files Changed
MODIFY /db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/i18n/I18NImportExport_app.properties
MODIFY /db/derby/code/trunk/java/tools/org/apache/derby/iapi/tools/i18n/LocalizedResource.java

Repository Revision Date User Message
ASF #264135 Mon Aug 29 13:14:13 UTC 2005 kmarsden merge change 239718 from the trunk.

DERBY-470 - Exception when using LOCALIZEDDISPLAY with JSR169

1. Check for BigDecimal class in the JVM by doing a Class.forName
2. Call getNumberAsString for NUMERIC and DECIMAL types only if BigDecimal class is available. Otherwise, return rs.getString.

                Contributed by Deepa Remesh
Files Changed
MODIFY /db/derby/code/branches/10.1/java/testing/org/apache/derbyTesting/functionTests/tests/i18n/I18NImportExport_app.properties
MODIFY /db/derby/code/branches/10.1/java/tools/org/apache/derby/iapi/tools/i18n/LocalizedResource.java