We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Bug in Java "Cell.getStringValue()" in aspose-cell-jdk1.5-7.0.3.jar


I am facing an issue when reading a cell's value "as a string" (Cell.getStringValue), whereas reading it's value as an object (Cell.getValue) would return the correct value with cell-7.0.3 for jdk-1.5 for Java.

Within my attached xls-file you can find a matrix with cells referencing a not-existing worksheet - but I do have to parse the allready containing values which works fine with most cells - but not with all of them.

I have also attached a little testfile where I compare a cell's value with it's string-value (allready with fixed beautyfiers).

(1) Cell "R4" is my GOOD example - here the string-value and the value are identical ("5587.13486816966").

(2) Cell "R5" is my BAD example - here the string-value is "9223.372036854777" (instead of "73549.10746874758").

An interesting fact to note is that EVERY TIME I am facing this string-value bug (within every other cells and excel-sheets) the returned, wrong string-value is ALLWAYS "9223.372036854777" (so this seems some kind of garbage not related to the cell or sheet at all).

My testfile produces the following output to stdout - and it's junit-testcase failes due to the differences in cell "R5" - please see the attached files for details.

R4 (getStringValue) = 5587.13486816966
R4 (getValue.toString) = 5587.13486816966
R5 (getStringValue) = 9223.372036854777
R5 (getValue.toString) = 73549.10746874758



Thanks for reporting this issue and using Aspose.Cells for Java.

I have tested your issue with the latest version:
Aspose.Cells for Java v7.0.4.2 and found the problem.

We will further look into it, we have logged it in our database. Once we will get update or fix, we will let you know asap.

This issue has been logged as CELLSJAVA-40093.


We have fixed this issue. Please download: Aspose.Cells for Java (Latest Version)

The issues you have found earlier (filed as CELLSJAVA-40093) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.