| Summary: | HSSFCell.setCellValue(String value) & HSSFRichTextString | ||
|---|---|---|---|
| Product: | POI | Reporter: | apache |
| Component: | HSSF | Assignee: | POI Developers List <dev> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | ||
| Priority: | P2 | ||
| Version: | 3.2-FINAL | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
Please try POI-3.5-beta7 or the latest trunk, the fix is already there:
public void setCellValue(String value) {
HSSFRichTextString str = value == null ? null : new HSSFRichTextString(value);
setCellValue(str);
}
Yegor
|
The now deprecated method HSSFCell.setCellValue(String value) has been changed to call the new method setCellValue(HSSFRichTextString value) with a HSSFRichTextString Object. The problem with that, is that a null String gets replaced with a HSSFRichTextString Object with the value "" (i.e. length 0). This broke our application, which I have fixed by calling setCellValue((HSSFRichTextString)null) I believe the correct implementation of HSSFCell.setCellValue(String value) should be: if (value == null) { setCellValue((HSSFRichTextString)null); } else { setCellValue(new HSSFRichTextString(value)); } This would be much more likely to be backward compatible with existing code. I'm sure others will be having this problem, but have maybe not yet noticed the subtle difference in their reports. Best regards, DaveLaw